Downlink Control Reception based on Small Data Transmission

ABSTRACT

A wireless device receives a radio resource control (RRC) release message indicating one or more configured grants for small data transmission (SDT) in an RRC inactive state and one or more synchronization signal and physical broadcast channel blocks (SSBs) used for the SDT. The wireless device receives downlink control information based on a demodulation reference signal (DM-RS) antenna port for downlink control channel reception being quasi co-located with an SSB, of the one or more SSBs, selected during a most recent SDT, wherein the downlink control information indicates uplink radio resources. The wireless device transmits a transport block via the uplink radio resources.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of International Application No.PCT/US2022/012507, filed Jan. 14, 2022, which claims the benefit of U.S.Provisional Application No. 63/137,657, filed Jan. 14, 2021, which arehereby incorporated by reference in their entireties.

BRIEF DESCRIPTION OF THE DRAWINGS

Examples of several of the various embodiments of the present disclosureare described herein with reference to the drawings.

FIG. 1A and FIG. 1B illustrate example mobile communication networks inwhich embodiments of the present disclosure may be implemented.

FIG. 2A and FIG. 2B respectively illustrate a New Radio (NR) user planeand control plane protocol stack.

FIG. 3 illustrates an example of services provided between protocollayers of the NR user plane protocol stack of FIG. 2A.

FIG. 4A illustrates an example downlink data flow through the NR userplane protocol stack of FIG. 2A.

FIG. 4B illustrates an example format of a MAC subheader in a MAC PDU.

FIG. 5A and FIG. 5B respectively illustrate a mapping between logicalchannels, transport channels, and physical channels for the downlink anduplink.

FIG. 6 is an example diagram showing RRC state transitions of a UE.

FIG. 7 illustrates an example configuration of an NR frame into whichOFDM symbols are grouped.

FIG. 8 illustrates an example configuration of a slot in the time andfrequency domain for an NR carrier.

FIG. 9 illustrates an example of bandwidth adaptation using threeconfigured BWPs for an NR carrier.

FIG. 10A illustrates three carrier aggregation configurations with twocomponent carriers.

FIG. 10B illustrates an example of how aggregated cells may beconfigured into one or more PUCCH groups.

FIG. 11A illustrates an example of an SS/PBCH block structure andlocation.

FIG. 11B illustrates an example of CSI-RSs that are mapped in the timeand frequency domains.

FIG. 12A and FIG. 12B respectively illustrate examples of three downlinkand uplink beam management procedures.

FIG. 13A, FIG. 13B, and FIG. 13C respectively illustrate a four-stepcontention-based random access procedure, a two-step contention-freerandom access procedure, and another two-step random access procedure.

FIG. 14A illustrates an example of CORESET configurations for abandwidth part.

FIG. 14B illustrates an example of a CCE-to-REG mapping for DCItransmission on a CORESET and PDCCH processing.

FIG. 15 illustrates an example of a wireless device in communicationwith a base station.

FIG. 16A, FIG. 16B, FIG. 16C, and FIG. 16D illustrate example structuresfor uplink and downlink transmission.

FIG. 17 illustrates uplink data transmission in a Non-RRC_CONNECTEDstate, according to some embodiments.

FIG. 18A illustrates an RA-based SDT with a four-step RA procedure,according to some embodiments.

FIG. 18B illustrates an RA-based SDT with a two-step RA procedure,according to some embodiments.

FIG. 19A is an example of (pre-)configured grant(s) of one or moreuplink radio resources in a Non-RRC_CONNECTED state, according to someembodiments.

FIG. 19B is an example of (pre-)configured grant(s) indicating one ormore uplink radio resources in a Non-RRC_CONNECTED state, according tosome embodiments.

FIG. 20 is an example of one or more subsequent transmissions of an SDT,according to some embodiments.

FIG. 21 is an example of beam management for transmission and/orreception in a Non-RRC_CONNECTED state as per an aspect of an embodimentof the present disclosure.

FIG. 22 is an example of a determination of at least one RS fortransmission(s) in an RRC_CONNECTED state, according to someembodiments.

FIG. 23 is an example of a determination of a reference signal to beused for downlink reception(s) in the RRC_CONNECTED state, according tosome embodiments.

FIG. 24 is an example of a determination of a reference signal to beused for downlink reception(s) in the RRC_CONNECTED state, according tosome embodiments.

FIG. 25 is an example of a determination of a reference signal to beused for downlink reception(s) in the RRC_CONNECTED state, according tosome embodiments.

FIG. 26 is an example of a determination of a reference signal to beused for downlink reception(s) in the RRC_CONNECTED state, according tosome embodiments.

DETAILED DESCRIPTION

In the present disclosure, various embodiments are presented as examplesof how the disclosed techniques may be implemented and/or how thedisclosed techniques may be practiced in environments and scenarios. Itwill be apparent to persons skilled in the relevant art that variouschanges in form and detail can be made therein without departing fromthe scope. In fact, after reading the description, it will be apparentto one skilled in the relevant art how to implement alternativeembodiments. The present embodiments should not be limited by any of thedescribed exemplary embodiments. The embodiments of the presentdisclosure will be described with reference to the accompanyingdrawings. Limitations, features, and/or elements from the disclosedexample embodiments may be combined to create further embodiments withinthe scope of the disclosure. Any figures which highlight thefunctionality and advantages, are presented for example purposes only.The disclosed architecture is sufficiently flexible and configurable,such that it may be utilized in ways other than that shown. For example,the actions listed in any flowchart may be re-ordered or only optionallyused in some embodiments.

Embodiments may be configured to operate as needed. The disclosedmechanism may be performed when certain criteria are met, for example,in a wireless device, a base station, a radio environment, a network, acombination of the above, and/or the like. Example criteria may bebased, at least in part, on for example, wireless device or network nodeconfigurations, traffic load, initial system set up, packet sizes,traffic characteristics, a combination of the above, and/or the like.When the one or more criteria are met, various example embodiments maybe applied. Therefore, it may be possible to implement exampleembodiments that selectively implement disclosed protocols.

A base station may communicate with a mix of wireless devices. Wirelessdevices and/or base stations may support multiple technologies, and/ormultiple releases of the same technology. Wireless devices may have somespecific capability(ies) depending on wireless device category and/orcapability(ies). When this disclosure refers to a base stationcommunicating with a plurality of wireless devices, this disclosure mayrefer to a subset of the total wireless devices in a coverage area. Thisdisclosure may refer to, for example, a plurality of wireless devices ofa given LTE or 5G release with a given capability and in a given sectorof the base station. The plurality of wireless devices in thisdisclosure may refer to a selected plurality of wireless devices, and/ora subset of total wireless devices in a coverage area which performaccording to disclosed methods, and/or the like. There may be aplurality of base stations or a plurality of wireless devices in acoverage area that may not comply with the disclosed methods, forexample, those wireless devices or base stations may perform based onolder releases of LTE or 5G technology.

In this disclosure, “a” and “an” and similar phrases are to beinterpreted as “at least one” and “one or more.” Similarly, any termthat ends with the suffix “(s)” is to be interpreted as “at least one”and “one or more.” In this disclosure, the term “may” is to beinterpreted as “may, for example.” In other words, the term “may” isindicative that the phrase following the term “may” is an example of oneof a multitude of suitable possibilities that may, or may not, beemployed by one or more of the various embodiments. The terms“comprises” and “consists of”, as used herein, enumerate one or morecomponents of the element being described. The term “comprises” isinterchangeable with “includes” and does not exclude unenumeratedcomponents from being included in the element being described. Bycontrast, “consists of” provides a complete enumeration of the one ormore components of the element being described. The term “based on”, asused herein, should be interpreted as “based at least in part on” ratherthan, for example, “based solely on”. The term “and/or” as used hereinrepresents any possible combination of enumerated elements. For example,“A, B, and/or C” may represent A; B; C; A and B; A and C; B and C; or A,B, and C.

If A and B are sets and every element of A is an element of B, A iscalled a subset of B. In this specification, only non-empty sets andsubsets are considered. For example, possible subsets of B = {cell1,cell2} are: {cell1}, {cell2}, and {cell1, cell2}. The phrase “based on”(or equally “based at least on”) is indicative that the phrase followingthe term “based on” is an example of one of a multitude of suitablepossibilities that may, or may not, be employed to one or more of thevarious embodiments. The phrase “in response to” (or equally “inresponse at least to”) is indicative that the phrase following thephrase “in response to” is an example of one of a multitude of suitablepossibilities that may, or may not, be employed to one or more of thevarious embodiments. The phrase “depending on” (or equally “depending atleast to”) is indicative that the phrase following the phrase “dependingon” is an example of one of a multitude of suitable possibilities thatmay, or may not, be employed to one or more of the various embodiments.The phrase “employing/using” (or equally “employing/using at least”) isindicative that the phrase following the phrase “employing/using” is anexample of one of a multitude of suitable possibilities that may, or maynot, be employed to one or more of the various embodiments.

The term configured may relate to the capacity of a device whether thedevice is in an operational or non-operational state. Configured mayrefer to specific settings in a device that effect the operationalcharacteristics of the device whether the device is in an operational ornon-operational state. In other words, the hardware, software, firmware,registers, memory values, and/or the like may be “configured” within adevice, whether the device is in an operational or nonoperational state,to provide the device with specific characteristics. Terms such as “acontrol message to cause in a device” may mean that a control messagehas parameters that may be used to configure specific characteristics ormay be used to implement certain actions in the device, whether thedevice is in an operational or non-operational state.

In this disclosure, parameters (or equally called, fields, orInformation elements: IEs) may comprise one or more information objects,and an information object may comprise one or more other objects. Forexample, if parameter (IE) N comprises parameter (IE) M, and parameter(IE) M comprises parameter (IE) K, and parameter (IE) K comprisesparameter (information element) J. Then, for example, N comprises K, andN comprises J. In an example embodiment, when one or more messagescomprise a plurality of parameters, it implies that a parameter in theplurality of parameters is in at least one of the one or more messages,but does not have to be in each of the one or more messages.

Many features presented are described as being optional through the useof “may” or the use of parentheses. For the sake of brevity andlegibility, the present disclosure does not explicitly recite each andevery permutation that may be obtained by choosing from the set ofoptional features. The present disclosure is to be interpreted asexplicitly disclosing all such permutations. For example, a systemdescribed as having three optional features may be embodied in sevenways, namely with just one of the three possible features, with any twoof the three possible features or with three of the three possiblefeatures.

Many of the elements described in the disclosed embodiments may beimplemented as modules. A module is defined here as an element thatperforms a defined function and has a defined interface to otherelements. The modules described in this disclosure may be implemented inhardware, software in combination with hardware, firmware, wetware (e.g.hardware with a biological element) or a combination thereof, which maybe behaviorally equivalent. For example, modules may be implemented as asoftware routine written in a computer language configured to beexecuted by a hardware machine (such as C, C++, Fortran, Java, Basic,Matlab or the like) or a modeling/simulation program such as Simulink,Stateflow, GNU Octave, or LabVIEWMathScript. It may be possible toimplement modules using physical hardware that incorporates discrete orprogrammable analog, digital and/or quantum hardware. Examples ofprogrammable hardware comprise: computers, microcontrollers,microprocessors, application-specific integrated circuits (ASICs); fieldprogrammable gate arrays (FPGAs); and complex programmable logic devices(CPLDs). Computers, microcontrollers and microprocessors are programmedusing languages such as assembly, C, C++ or the like. FPGAs, ASICs andCPLDs are often programmed using hardware description languages (HDL)such as VHSIC hardware description language (VHDL) or Verilog thatconfigure connections between internal hardware modules with lesserfunctionality on a programmable device. The mentioned technologies areoften used in combination to achieve the result of a functional module.

FIG. 1A illustrates an example of a mobile communication network 100 inwhich embodiments of the present disclosure may be implemented. Themobile communication network 100 may be, for example, a public landmobile network (PLMN) run by a network operator. As illustrated in FIG.1A, the mobile communication network 100 includes a core network (CN)102, a radio access network (RAN) 104, and a wireless device 106.

The CN 102 may provide the wireless device 106 with an interface to oneor more data networks (DNs), such as public DNs (e.g., the Internet),private DNs, and/or intra-operator DNs. As part of the interfacefunctionality, the CN 102 may set up end-to-end connections between thewireless device 106 and the one or more DNs, authenticate the wirelessdevice 106, and provide charging functionality.

The RAN 104 may connect the CN 102 to the wireless device 106 throughradio communications over an air interface. As part of the radiocommunications, the RAN 104 may provide scheduling, radio resourcemanagement, and retransmission protocols. The communication directionfrom the RAN 104 to the wireless device 106 over the air interface isknown as the downlink and the communication direction from the wirelessdevice 106 to the RAN 104 over the air interface is known as the uplink.Downlink transmissions may be separated from uplink transmissions usingfrequency division duplexing (FDD), time-division duplexing (TDD),and/or some combination of the two duplexing techniques.

The term wireless device may be used throughout this disclosure to referto and encompass any mobile device or fixed (non-mobile) device forwhich wireless communication is needed or usable. For example, awireless device may be a telephone, smart phone, tablet, computer,laptop, sensor, meter, wearable device, Internet of Things (IoT) device,vehicle road side unit (RSU), relay node, automobile, and/or anycombination thereof. The term wireless device encompasses otherterminology, including user equipment (UE), user terminal (UT), accessterminal (AT), mobile station, handset, wireless transmit and receiveunit (WTRU), and/or wireless communication device.

The RAN 104 may include one or more base stations (not shown). The termbase station may be used throughout this disclosure to refer to andencompass a Node B (associated with UMTS and/or 3G standards), anEvolved Node B (eNB, associated with E-UTRA and/or 4G standards), aremote radio head (RRH), a baseband processing unit coupled to one ormore RRHs, a repeater node or relay node used to extend the coveragearea of a donor node, a Next Generation Evolved Node B (ng-eNB), aGeneration Node B (gNB, associated with NR and/or 5G standards), anaccess point (AP, associated with, for example, WiFi or any othersuitable wireless communication standard), and/or any combinationthereof. A base station may comprise at least one gNB Central Unit(gNB-CU) and at least one a gNB Distributed Unit (gNB-DU).

A base station included in the RAN 104 may include one or more sets ofantennas for communicating with the wireless device 106 over the airinterface. For example, one or more of the base stations may includethree sets of antennas to respectively control three cells (or sectors).The size of a cell may be determined by a range at which a receiver(e.g., a base station receiver) can successfully receive thetransmissions from a transmitter (e.g., a wireless device transmitter)operating in the cell. Together, the cells of the base stations mayprovide radio coverage to the wireless device 106 over a wide geographicarea to support wireless device mobility.

In addition to three-sector sites, other implementations of basestations are possible. For example, one or more of the base stations inthe RAN 104 may be implemented as a sectored site with more or less thanthree sectors. One or more of the base stations in the RAN 104 may beimplemented as an access point, as a baseband processing unit coupled toseveral remote radio heads (RRHs), and/or as a repeater or relay nodeused to extend the coverage area of a donor node. A baseband processingunit coupled to RRHs may be part of a centralized or cloud RANarchitecture, where the baseband processing unit may be eithercentralized in a pool of baseband processing units or virtualized. Arepeater node may amplify and rebroadcast a radio signal received from adonor node. A relay node may perform the same/similar functions as arepeater node but may decode the radio signal received from the donornode to remove noise before amplifying and rebroadcasting the radiosignal.

The RAN 104 may be deployed as a homogenous network of macrocell basestations that have similar antenna patterns and similar high-leveltransmit powers. The RAN 104 may be deployed as a heterogeneous network.In heterogeneous networks, small cell base stations may be used toprovide small coverage areas, for example, coverage areas that overlapwith the comparatively larger coverage areas provided by macrocell basestations. The small coverage areas may be provided in areas with highdata traffic (or so-called “hotspots”) or in areas with weak macrocellcoverage. Examples of small cell base stations include, in order ofdecreasing coverage area, microcell base stations, picocell basestations, and femtocell base stations or home base stations.

The Third-Generation Partnership Project (3GPP) was formed in 1998 toprovide global standardization of specifications for mobilecommunication networks similar to the mobile communication network 100in FIG. 1A. To date, 3GPP has produced specifications for threegenerations of mobile networks: a third generation (3G) network known asUniversal Mobile Telecommunications System (UMTS), a fourth generation(4G) network known as Long-Term Evolution (LTE), and a fifth generation(5G) network known as 5G System (5GS). Embodiments of the presentdisclosure are described with reference to the RAN of a 3GPP 5G network,referred to as next-generation RAN (NG-RAN). Embodiments may beapplicable to RANs of other mobile communication networks, such as theRAN 104 in FIG. 1A, the RANs of earlier 3G and 4G networks, and those offuture networks yet to be specified (e.g., a 3GPP 6G network). NG-RANimplements 5G radio access technology known as New Radio (NR) and may beprovisioned to implement 4G radio access technology or other radioaccess technologies, including non-3GPP radio access technologies.

FIG. 1B illustrates another example mobile communication network 150 inwhich embodiments of the present disclosure may be implemented. Mobilecommunication network 150 may be, for example, a PLMN run by a networkoperator. As illustrated in FIG. 1B, mobile communication network 150includes a 5G core network (5G-CN) 152, an NG-RAN 154, and UEs 156A and156B (collectively UEs 156). These components may be implemented andoperate in the same or similar manner as corresponding componentsdescribed with respect to FIG. 1A.

The 5G-CN 152 provides the UEs 156 with an interface to one or more DNs,such as public DNs (e.g., the Internet), private DNs, and/orintra-operator DNs. As part of the interface functionality, the 5G-CN152 may set up end-to-end connections between the UEs 156 and the one ormore DNs, authenticate the UEs 156, and provide charging functionality.Compared to the CN of a 3GPP 4G network, the basis of the 5G-CN 152 maybe a service-based architecture. This means that the architecture of thenodes making up the 5G-CN 152 may be defined as network functions thatoffer services via interfaces to other network functions. The networkfunctions of the 5G-CN 152 may be implemented in several ways, includingas network elements on dedicated or shared hardware, as softwareinstances running on dedicated or shared hardware, or as virtualizedfunctions instantiated on a platform (e.g., a cloud-based platform).

As illustrated in FIG. 1B, the 5G-CN 152 includes an Access and MobilityManagement Function (AMF) 158A and a User Plane Function (UPF) 158B,which are shown as one component AMF/UPF 158 in FIG. 1B for ease ofillustration. The UPF 158B may serve as a gateway between the NG-RAN 154and the one or more DNs. The UPF 158B may perform functions such aspacket routing and forwarding, packet inspection and user plane policyrule enforcement, traffic usage reporting, uplink classification tosupport routing of traffic flows to the one or more DNs, quality ofservice (QoS) handling for the user plane (e.g., packet filtering,gating, uplink/downlink rate enforcement, and uplink trafficverification), downlink packet buffering, and downlink data notificationtriggering. The UPF 158B may serve as an anchor point forintra-/inter-Radio Access Technology (RAT) mobility, an externalprotocol (or packet) data unit (PDU) session point of interconnect tothe one or more DNs, and/or a branching point to support a multi-homedPDU session. The UEs 156 may be configured to receive services through aPDU session, which is a logical connection between a UE and a DN.

The AMF 158A may perform functions such as Non-Access Stratum (NAS)signaling termination, NAS signaling security, Access Stratum (AS)security control, inter-CN node signaling for mobility between 3GPPaccess networks, idle mode UE reachability (e.g., control and executionof paging retransmission), registration area management, intra-systemand intersystem mobility support, access authentication, accessauthorization including checking of roaming rights, mobility managementcontrol (subscription and policies), network slicing support, and/orsession management function (SMF) selection. NAS may refer to thefunctionality operating between a CN and a UE, and AS may refer to thefunctionality operating between the UE and a RAN.

The 5G-CN 152 may include one or more additional network functions thatare not shown in FIG. 1B for the sake of clarity. For example, the 5G-CN152 may include one or more of a Session Management Function (SMF), anNR Repository Function (NRF), a Policy Control Function (PCF), a NetworkExposure Function (NEF), a Unified Data Management (UDM), an ApplicationFunction (AF), and/or an Authentication Server Function (AUSF).

The NG-RAN 154 may connect the 5G-CN 152 to the UEs 156 through radiocommunications over the air interface. The NG-RAN 154 may include one ormore gNBs, illustrated as gNB 160A and gNB 160B (collectively gNBs 160)and/or one or more ng-eNBs, illustrated as ng-eNB 162A and ng-eNB 162B(collectively ng-eNBs 162). The gNBs 160 and ng-eNBs 162 may be moregenerically referred to as base stations. The gNBs 160 and ng-eNBs 162may include one or more sets of antennas for communicating with the UEs156 over an air interface. For example, one or more of the gNBs 160and/or one or more of the ng-eNBs 162 may include three sets of antennasto respectively control three cells (or sectors). Together, the cells ofthe gNBs 160 and the ng-eNBs 162 may provide radio coverage to the UEs156 over a wide geographic area to support UE mobility.

As shown in FIG. 1B, the gNBs 160 and/or the ng-eNBs 162 may beconnected to the 5G-CN 152 by means of an NG interface and to other basestations by an Xn interface. The NG and Xn interfaces may be establishedusing direct physical connections and/or indirect connections over anunderlying transport network, such as an internet protocol (IP)transport network. The gNBs 160 and/or the ng-eNBs 162 may be connectedto the UEs 156 by means of a Uu interface. For example, as illustratedin FIG. 1B, gNB 160A may be connected to the UE 156A by means of a Uuinterface. The NG, Xn, and Uu interfaces are associated with a protocolstack. The protocol stacks associated with the interfaces may be used bythe network elements in FIG. 1B to exchange data and signaling messagesand may include two planes: a user plane and a control plane. The userplane may handle data of interest to a user. The control plane mayhandle signaling messages of interest to the network elements.

The gNBs 160 and/or the ng-eNBs 162 may be connected to one or moreAMF/UPF functions of the 5G-CN 152, such as the AMF/UPF 158, by means ofone or more NG interfaces. For example, the gNB 160A may be connected tothe UPF 158B of the AMF/UPF 158 by means of an NG-User plane (NG-U)interface. The NG-U interface may provide delivery (e.g., non-guaranteeddelivery) of user plane PDUs between the gNB 160A and the UPF 158B. ThegNB 160A may be connected to the AMF 158A by means of an NG-Controlplane (NG-C) interface. The NG-C interface may provide, for example, NGinterface management, UE context management, UE mobility management,transport of NAS messages, paging, PDU session management, andconfiguration transfer and/or warning message transmission.

The gNBs 160 may provide NR user plane and control plane protocolterminations towards the UEs 156 over the Uu interface. For example, thegNB 160A may provide NR user plane and control plane protocolterminations toward the UE 156A over a Uu interface associated with afirst protocol stack. The ng-eNBs 162 may provide Evolved UMTSTerrestrial Radio Access (E-UTRA) user plane and control plane protocolterminations towards the UEs 156 over a Uu interface, where E-UTRArefers to the 3GPP 4G radio-access technology. For example, the ng-eNB162B may provide E-UTRA user plane and control plane protocolterminations towards the UE 156B over a Uu interface associated with asecond protocol stack.

The 5G-CN 152 was described as being configured to handle NR and 4Gradio accesses. It will be appreciated by one of ordinary skill in theart that it may be possible for NR to connect to a 4G core network in amode known as “non-standalone operation.” In non-standalone operation, a4G core network is used to provide (or at least support) control-planefunctionality (e.g., initial access, mobility, and paging). Althoughonly one AMF/UPF 158 is shown in FIG. 1B, one gNB or ng-eNB may beconnected to multiple AMF/UPF nodes to provide redundancy and/or to loadshare across the multiple AMF/UPF nodes.

As discussed, an interface (e.g., Uu, Xn, and NG interfaces) between thenetwork elements in FIG. 1B may be associated with a protocol stack thatthe network elements use to exchange data and signaling messages. Aprotocol stack may include two planes: a user plane and a control plane.The user plane may handle data of interest to a user, and the controlplane may handle signaling messages of interest to the network elements.

FIG. 2A and FIG. 2B respectively illustrate examples of NR user planeand NR control plane protocol stacks for the Uu interface that liesbetween a UE 210 and a gNB 220. The protocol stacks illustrated in FIG.2A and FIG. 2B may be the same or similar to those used for the Uuinterface between, for example, the UE 156A and the gNB 160A shown inFIG. 1B.

FIG. 2A illustrates a NR user plane protocol stack comprising fivelayers implemented in the UE 210 and the gNB 220. At the bottom of theprotocol stack, physical layers (PHYs) 211 and 221 may provide transportservices to the higher layers of the protocol stack and may correspondto layer 1 of the Open Systems Interconnection (OSI) model. The nextfour protocols above PHYs 211 and 221 comprise media access controllayers (MACs) 212 and 222, radio link control layers (RLCs) 213 and 223,packet data convergence protocol layers (PDCPs) 214 and 224, and servicedata application protocol layers (SDAPs) 215 and 225. Together, thesefour protocols may make up layer 2, or the data link layer, of the OSImodel.

FIG. 3 illustrates an example of services provided between protocollayers of the NR user plane protocol stack. Starting from the top ofFIG. 2A and FIG. 3 , the SDAPs 215 and 225 may perform QoS flowhandling. The UE 210 may receive services through a PDU session, whichmay be a logical connection between the UE 210 and a DN. The PDU sessionmay have one or more QoS flows. A UPF of a CN (e.g., the UPF 158B) maymap IP packets to the one or more QoS flows of the PDU session based onQoS requirements (e.g., in terms of delay, data rate, and/or errorrate). The SDAPs 215 and 225 may perform mapping/de-mapping between theone or more QoS flows and one or more data radio bearers. Themapping/de-mapping between the QoS flows and the data radio bearers maybe determined by the SDAP 225 at the gNB 220. The SDAP 215 at the UE 210may be informed of the mapping between the QoS flows and the data radiobearers through reflective mapping or control signaling received fromthe gNB 220. For reflective mapping, the SDAP 225 at the gNB 220 maymark the downlink packets with a QoS flow indicator (QFI), which may beobserved by the SDAP 215 at the UE 210 to determine themapping/de-mapping between the QoS flows and the data radio bearers.

The PDCPs 214 and 224 may perform header compression/decompression toreduce the amount of data that needs to be transmitted over the airinterface, ciphering/deciphering to prevent unauthorized decoding ofdata transmitted over the air interface, and integrity protection (toensure control messages originate from intended sources. The PDCPs 214and 224 may perform retransmissions of undelivered packets, in-sequencedelivery and reordering of packets, and removal of packets received induplicate due to, for example, an intra-gNB handover. The PDCPs 214 and224 may perform packet duplication to improve the likelihood of thepacket being received and, at the receiver, remove any duplicatepackets. Packet duplication may be useful for services that require highreliability.

Although not shown in FIG. 3 , PDCPs 214 and 224 may performmapping/de-mapping between a split radio bearer and RLC channels in adual connectivity scenario. Dual connectivity is a technique that allowsa UE to connect to two cells or, more generally, two cell groups: amaster cell group (MCG) and a secondary cell group (SCG). A split beareris when a single radio bearer, such as one of the radio bearers providedby the PDCPs 214 and 224 as a service to the SDAPs 215 and 225, ishandled by cell groups in dual connectivity. The PDCPs 214 and 224 maymap/de-map the split radio bearer between RLC channels belonging to cellgroups.

The RLCs 213 and 223 may perform segmentation, retransmission throughAutomatic Repeat Request (ARQ), and removal of duplicate data unitsreceived from MACs 212 and 222, respectively. The RLCs 213 and 223 maysupport three transmission modes: transparent mode (TM); unacknowledgedmode (UM); and acknowledged mode (AM). Based on the transmission mode anRLC is operating, the RLC may perform one or more of the notedfunctions. The RLC configuration may be per logical channel with nodependency on numerologies and/or Transmission Time Interval (TTI)durations. As shown in FIG. 3 , the RLCs 213 and 223 may provide RLCchannels as a service to PDCPs 214 and 224, respectively.

The MACs 212 and 222 may perform multiplexing/demultiplexing of logicalchannels and/or mapping between logical channels and transport channels.The multiplexing/demultiplexing may include multiplexing/demultiplexingof data units, belonging to the one or more logical channels, into/fromTransport Blocks (TBs) delivered to/from the PHYs 211 and 221. The MAC222 may be configured to perform scheduling, scheduling informationreporting, and priority handling between UEs by means of dynamicscheduling. Scheduling may be performed in the gNB 220 (at the MAC 222)for downlink and uplink. The MACs 212 and 222 may be configured toperform error correction through Hybrid Automatic Repeat Request (HARQ)(e.g., one HARQ entity per carrier in case of Carrier Aggregation (CA)),priority handling between logical channels of the UE 210 by means oflogical channel prioritization, and/or padding. The MACs 212 and 222 maysupport one or more numerologies and/or transmission timings. In anexample, mapping restrictions in a logical channel prioritization maycontrol which numerology and/or transmission timing a logical channelmay use. As shown in FIG. 3 , the MACs 212 and 222 may provide logicalchannels as a service to the RLCs 213 and 223.

The PHYs 211 and 221 may perform mapping of transport channels tophysical channels and digital and analog signal processing functions forsending and receiving information over the air interface. These digitaland analog signal processing functions may include, for example,coding/decoding and modulation/demodulation. The PHYs 211 and 221 mayperform multi-antenna mapping. As shown in FIG. 3 , the PHYs 211 and 221may provide one or more transport channels as a service to the MACs 212and 222.

FIG. 4A illustrates an example downlink data flow through the NR userplane protocol stack. FIG. 4A illustrates a downlink data flow of threeIP packets (n, n+1, and m) through the NR user plane protocol stack togenerate two TBs at the gNB 220. An uplink data flow through the NR userplane protocol stack may be similar to the downlink data flow depictedin FIG. 4A.

The downlink data flow of FIG. 4A begins when SDAP 225 receives thethree IP packets from one or more QoS flows and maps the three packetsto radio bearers. In FIG. 4A, the SDAP 225 maps IP packets n and n+1 toa first radio bearer 402 and maps IP packet m to a second radio bearer404. An SDAP header (labeled with an “H” in FIG. 4A) is added to an IPpacket. The data unit from/to a higher protocol layer is referred to asa service data unit (SDU) of the lower protocol layer and the data unitto/from a lower protocol layer is referred to as a protocol data unit(PDU) of the higher protocol layer. As shown in FIG. 4A, the data unitfrom the SDAP 225 is an SDU of lower protocol layer PDCP 224 and is aPDU of the SDAP 225.

The remaining protocol layers in FIG. 4A may perform their associatedfunctionality (e.g., with respect to FIG. 3 ), add correspondingheaders, and forward their respective outputs to the next lower layer.For example, the PDCP 224 may perform IP-header compression andciphering and forward its output to the RLC 223. The RLC 223 mayoptionally perform segmentation (e.g., as shown for IP packet m in FIG.4A) and forward its output to the MAC 222. The MAC 222 may multiplex anumber of RLC PDUs and may attach a MAC subheader to an RLC PDU to forma transport block. In NR, the MAC subheaders may be distributed acrossthe MAC PDU, as illustrated in FIG. 4A. In LTE, the MAC subheaders maybe entirely located at the beginning of the MAC PDU. The NR MAC PDUstructure may reduce processing time and associated latency because theMAC PDU subheaders may be computed before the full MAC PDU is assembled.

FIG. 4B illustrates an example format of a MAC subheader in a MAC PDU.The MAC subheader includes: an SDU length field for indicating thelength (e.g., in bytes) of the MAC SDU to which the MAC subheadercorresponds; a logical channel identifier (LCID) field for identifyingthe logical channel from which the MAC SDU originated to aid in thedemultiplexing process; a flag (F) for indicating the size of the SDUlength field; and a reserved bit (R) field for future use.

FIG. 4B further illustrates MAC control elements (CEs) inserted into theMAC PDU by a MAC, such as MAC 223 or MAC 222. For example, FIG. 4Billustrates two MAC CEs inserted into the MAC PDU. MAC CEs may beinserted at the beginning of a MAC PDU for downlink transmissions (asshown in FIG. 4B) and at the end of a MAC PDU for uplink transmissions.MAC CEs may be used for in-band control signaling. Example MAC CEsinclude: scheduling-related MAC CEs, such as buffer status reports andpower headroom reports; activation/deactivation MAC CEs, such as thosefor activation/deactivation of PDCP duplication detection, channel stateinformation (CSI) reporting, sounding reference signal (SRS)transmission, and prior configured components; discontinuous reception(DRX) related MAC CEs; timing advance MAC CEs; and random access relatedMAC CEs. A MAC CE may be preceded by a MAC subheader with a similarformat as described for MAC SDUs and may be identified with a reservedvalue in the LCID field that indicates the type of control informationincluded in the MAC CE.

Before describing the NR control plane protocol stack, logical channels,transport channels, and physical channels are first described as well asa mapping between the channel types. One or more of the channels may beused to carry out functions associated with the NR control planeprotocol stack described later below.

FIG. 5A and FIG. 5B illustrate, for downlink and uplink respectively, amapping between logical channels, transport channels, and physicalchannels. Information is passed through channels between the RLC, theMAC, and the PHY of the NR protocol stack. A logical channel may be usedbetween the RLC and the MAC and may be classified as a control channelthat carries control and configuration information in the NR controlplane or as a traffic channel that carries data in the NR user plane. Alogical channel may be classified as a dedicated logical channel that isdedicated to a specific UE or as a common logical channel that may beused by more than one UE. A logical channel may also be defined by thetype of information it carries. The set of logical channels defined byNR include, for example:

-   a paging control channel (PCCH) for carrying paging messages used to    page a UE whose location is not known to the network on a cell    level;-   a broadcast control channel (BCCH) for carrying system information    messages in the form of a master information block (MIB) and several    system information blocks (SIBs), wherein the system information    messages may be used by the UEs to obtain information about how a    cell is configured and how to operate within the cell;-   a common control channel (CCCH) for carrying control messages    together with random access;-   a dedicated control channel (DCCH) for carrying control messages    to/from a specific the UE to configure the UE; and-   a dedicated traffic channel (DTCH) for carrying user data to/from a    specific the UE.

Transport channels are used between the MAC and PHY layers and may bedefined by how the information they carry is transmitted over the airinterface. The set of transport channels defined by NR include, forexample:

-   a paging channel (PCH) for carrying paging messages that originated    from the PCCH;-   a broadcast channel (BCH) for carrying the MIB from the BCCH;-   a downlink shared channel (DL-SCH) for carrying downlink data and    signaling messages, including the SIBs from the BCCH;-   an uplink shared channel (UL-SCH) for carrying uplink data and    signaling messages; and-   a random access channel (RACH) for allowing a UE to contact the    network without any prior scheduling.

The PHY may use physical channels to pass information between processinglevels of the PHY. A physical channel may have an associated set oftime-frequency resources for carrying the information of one or moretransport channels. The PHY may generate control information to supportthe low-level operation of the PHY and provide the control informationto the lower levels of the PHY via physical control channels, known asL1/L2 control channels. The set of physical channels and physicalcontrol channels defined by NR include, for example:

-   a physical broadcast channel (PBCH) for carrying the MIB from the    BCH;-   a physical downlink shared channel (PDSCH) for carrying downlink    data and signaling messages from the DL-SCH, as well as paging    messages from the PCH;-   a physical downlink control channel (PDCCH) for carrying downlink    control information (DCI), which may include downlink scheduling    commands, uplink scheduling grants, and uplink power control    commands;-   a physical uplink shared channel (PUSCH) for carrying uplink data    and signaling messages from the UL-SCH and in some instances uplink    control information (UCI) as described below;-   a physical uplink control channel (PUCCH) for carrying UCI, which    may include HARQ acknowledgments, channel quality indicators (CQI),    pre-coding matrix indicators (PMI), rank indicators (RI), and    scheduling requests (SR); and-   a physical random access channel (PRACH) for random access.

Similar to the physical control channels, the physical layer generatesphysical signals to support the low-level operation of the physicallayer. As shown in FIG. 5A and FIG. 5B, the physical layer signalsdefined by NR include: primary synchronization signals (PSS), secondarysynchronization signals (SSS), channel state information referencesignals (CSI-RS), demodulation reference signals (DMRS), soundingreference signals (SRS), and phase-tracking reference signals (PT-RS).These physical layer signals will be described in greater detail below.

FIG. 2B illustrates an example NR control plane protocol stack. As shownin FIG. 2B, the NR control plane protocol stack may use the same/similarfirst four protocol layers as the example NR user plane protocol stack.These four protocol layers include the PHYs 211 and 221, the MACs 212and 222, the RLCs 213 and 223, and the PDCPs 214 and 224. Instead ofhaving the SDAPs 215 and 225 at the top of the stack as in the NR userplane protocol stack, the NR control plane stack has radio resourcecontrols (RRCs) 216 and 226 and NAS protocols 217 and 237 at the top ofthe NR control plane protocol stack.

The NAS protocols 217 and 237 may provide control plane functionalitybetween the UE 210 and the AMF 230 (e.g., the AMF 158A) or, moregenerally, between the UE 210 and the CN. The NAS protocols 217 and 237may provide control plane functionality between the UE 210 and the AMF230 via signaling messages, referred to as NAS messages. There is nodirect path between the UE 210 and the AMF 230 through which the NASmessages can be transported. The NAS messages may be transported usingthe AS of the Uu and NG interfaces. NAS protocols 217 and 237 mayprovide control plane functionality such as authentication, security,connection setup, mobility management, and session management.

The RRCs 216 and 226 may provide control plane functionality between theUE 210 and the gNB 220 or, more generally, between the UE 210 and theRAN. The RRCs 216 and 226 may provide control plane functionalitybetween the UE 210 and the gNB 220 via signaling messages, referred toas RRC messages. RRC messages may be transmitted between the UE 210 andthe RAN using signaling radio bearers and the same/similar PDCP, RLC,MAC, and PHY protocol layers. The MAC may multiplex control-plane anduser-plane data into the same transport block (TB). The RRCs 216 and 226may provide control plane functionality such as: broadcast of systeminformation related to AS and NAS; paging initiated by the CN or theRAN; establishment, maintenance and release of an RRC connection betweenthe UE 210 and the RAN; security functions including key management;establishment, configuration, maintenance and release of signaling radiobearers and data radio bearers; mobility functions; QoS managementfunctions; the UE measurement reporting and control of the reporting;detection of and recovery from radio link failure (RLF); and/or NASmessage transfer. As part of establishing an RRC connection, RRCs 216and 226 may establish an RRC context, which may involve configuringparameters for communication between the UE 210 and the RAN.

FIG. 6 is an example diagram showing RRC state transitions of a UE. TheUE may be the same or similar to the wireless device 106 depicted inFIG. 1A, the UE 210 depicted in FIG. 2A and FIG. 2B, or any otherwireless device described in the present disclosure. As illustrated inFIG. 6 , a UE may be in at least one of three RRC states: RRC connected602 (e.g., RRC_CONNECTED), RRC idle 604 (e.g., RRC_IDLE), and RRCinactive 606 (e.g., RRC_INACTIVE).

In RRC connected 602, the UE has an established RRC context and may haveat least one RRC connection with a base station. The base station may besimilar to one of the one or more base stations included in the RAN 104depicted in FIG. 1A, one of the gNBs 160 or ng-eNBs 162 depicted in FIG.1B, the gNB 220 depicted in FIG. 2A and FIG. 2B, or any other basestation described in the present disclosure. The base station with whichthe UE is connected may have the RRC context for the UE. The RRCcontext, referred to as the UE context, may comprise parameters forcommunication between the UE and the base station. These parameters mayinclude, for example: one or more AS contexts; one or more radio linkconfiguration parameters; bearer configuration information (e.g.,relating to a data radio bearer, signaling radio bearer, logicalchannel, QoS flow, and/or PDU session); security information; and/orPHY, MAC, RLC, PDCP, and/or SDAP layer configuration information. Whilein RRC connected 602, mobility of the UE may be managed by the RAN(e.g., the RAN 104 or the NG-RAN 154). The UE may measure the signallevels (e.g., reference signal levels) from a serving cell andneighboring cells and report these measurements to the base stationcurrently serving the UE. The UE’s serving base station may request ahandover to a cell of one of the neighboring base stations based on thereported measurements. The RRC state may transition from RRC connected602 to RRC idle 604 through a connection release procedure 608 or to RRCinactive 606 through a connection inactivation procedure 610.

In RRC idle 604, an RRC context may not be established for the UE. InRRC idle 604, the UE may not have an RRC connection with the basestation. While in RRC idle 604, the UE may be in a sleep state for themajority of the time (e.g., to conserve battery power). The UE may wakeup periodically (e.g., once in every discontinuous reception cycle) tomonitor for paging messages from the RAN. Mobility of the UE may bemanaged by the UE through a procedure known as cell reselection. The RRCstate may transition from RRC idle 604 to RRC connected 602 through aconnection establishment procedure 612, which may involve a randomaccess procedure as discussed in greater detail below.

In RRC inactive 606, the RRC context previously established ismaintained in the UE and the base station. This allows for a fasttransition to RRC connected 602 with reduced signaling overhead ascompared to the transition from RRC idle 604 to RRC connected 602. Whilein RRC inactive 606, the UE may be in a sleep state and mobility of theUE may be managed by the UE through cell reselection. The RRC state maytransition from RRC inactive 606 to RRC connected 602 through aconnection resume procedure 614 or to RRC idle 604 though a connectionrelease procedure 616 that may be the same as or similar to connectionrelease procedure 608.

An RRC state may be associated with a mobility management mechanism. InRRC idle 604 and RRC inactive 606, mobility is managed by the UE throughcell reselection. The purpose of mobility management in RRC idle 604 andRRC inactive 606 is to allow the network to be able to notify the UE ofan event via a paging message without having to broadcast the pagingmessage over the entire mobile communications network. The mobilitymanagement mechanism used in RRC idle 604 and RRC inactive 606 may allowthe network to track the UE on a cell-group level so that the pagingmessage may be broadcast over the cells of the cell group that the UEcurrently resides within instead of the entire mobile communicationnetwork. The mobility management mechanisms for RRC idle 604 and RRCinactive 606 track the UE on a cell-group level. They may do so usingdifferent granularities of grouping. For example, there may be threelevels of cell-grouping granularity: individual cells; cells within aRAN area identified by a RAN area identifier (RAI); and cells within agroup of RAN areas, referred to as a tracking area and identified by atracking area identifier (TAI).

Tracking areas may be used to track the UE at the CN level. The CN(e.g., the CN 102 or the 5G-CN 152) may provide the UE with a list ofTAIs associated with a UE registration area. If the UE moves, throughcell reselection, to a cell associated with a TAI not included in thelist of TAIs associated with the UE registration area, the UE mayperform a registration update with the CN to allow the CN to update theUE’s location and provide the UE with a new the UE registration area.

RAN areas may be used to track the UE at the RAN level. For a UE in RRCinactive 606 state, the UE may be assigned a RAN notification area. ARAN notification area may comprise one or more cell identities, a listof RAIs, or a list of TAIs. In an example, a base station may belong toone or more RAN notification areas. In an example, a cell may belong toone or more RAN notification areas. If the UE moves, through cellreselection, to a cell not included in the RAN notification areaassigned to the UE, the UE may perform a notification area update withthe RAN to update the UE’s RAN notification area.

A base station storing an RRC context for a UE or a last serving basestation of the UE may be referred to as an anchor base station. Ananchor base station may maintain an RRC context for the UE at leastduring a period of time that the UE stays in a RAN notification area ofthe anchor base station and/or during a period of time that the UE staysin RRC inactive 606.

A gNB, such as gNBs 160 in FIG. 1B, may be split in two parts: a centralunit (gNB-CU), and one or more distributed units (gNB-DU). A gNB-CU maybe coupled to one or more gNB-DUs using an F1 interface. The gNB-CU maycomprise the RRC, the PDCP, and the SDAP. A gNB-DU may comprise the RLC,the MAC, and the PHY.

In NR, the physical signals and physical channels (discussed withrespect to FIG. 5A and FIG. 5B) may be mapped onto orthogonal frequencydivisional multiplexing (OFDM) symbols. OFDM is a multicarriercommunication scheme that transmits data over F orthogonal subcarriers(or tones). Before transmission, the data may be mapped to a series ofcomplex symbols (e.g., M-quadrature amplitude modulation (M-QAM) orM-phase shift keying (M-PSK) symbols), referred to as source symbols,and divided into F parallel symbol streams. The F parallel symbolstreams may be treated as though they are in the frequency domain andused as inputs to an Inverse Fast Fourier Transform (IFFT) block thattransforms them into the time domain. The IFFT block may take in Fsource symbols at a time, one from each of the F parallel symbolstreams, and use each source symbol to modulate the amplitude and phaseof one of F sinusoidal basis functions that correspond to the Forthogonal subcarriers. The output of the IFFT block may be Ftime-domain samples that represent the summation of the F orthogonalsubcarriers. The F time-domain samples may form a single OFDM symbol.After some processing (e.g., addition of a cyclic prefix) andup-conversion, an OFDM symbol provided by the IFFT block may betransmitted over the air interface on a carrier frequency. The Fparallel symbol streams may be mixed using an FFT block before beingprocessed by the IFFT block. This operation produces Discrete FourierTransform (DFT)-precoded OFDM symbols and may be used by UEs in theuplink to reduce the peak to average power ratio (PAPR). Inverseprocessing may be performed on the OFDM symbol at a receiver using anFFT block to recover the data mapped to the source symbols.

FIG. 7 illustrates an example configuration of an NR frame into whichOFDM symbols are grouped. An NR frame may be identified by a systemframe number (SFN). The SFN may repeat with a period of 1024 frames. Asillustrated, one NR frame may be 10 milliseconds (ms) in duration andmay include 10 subframes that are 1 ms in duration. A subframe may bedivided into slots that include, for example, 14 OFDM symbols per slot.

The duration of a slot may depend on the numerology used for the OFDMsymbols of the slot. In NR, a flexible numerology is supported toaccommodate different cell deployments (e.g., cells with carrierfrequencies below 1 GHz up to cells with carrier frequencies in themm-wave range). A numerology may be defined in terms of subcarrierspacing and cyclic prefix duration. For a numerology in NR, subcarrierspacings may be scaled up by powers of two from a baseline subcarrierspacing of 15 kHz, and cyclic prefix durations may be scaled down bypowers of two from a baseline cyclic prefix duration of 4.7 µs. Forexample, NR defines numerologies with the following subcarrierspacing/cyclic prefix duration combinations: 15 kHz/4.7 µs; 30 kHz/2.3µs; 60 kHz/1.2 µs; 120 kHz/0.59 µs; and 240 kHz/0.29 µs.

A slot may have a fixed number of OFDM symbols (e.g., 14 OFDM symbols).A numerology with a higher subcarrier spacing has a shorter slotduration and, correspondingly, more slots per subframe. FIG. 7illustrates this numerology-dependent slot duration andslots-per-subframe transmission structure (the numerology with asubcarrier spacing of 240 kHz is not shown in FIG. 7 for ease ofillustration). A subframe in NR may be used as a numerology-independenttime reference, while a slot may be used as the unit upon which uplinkand downlink transmissions are scheduled. To support low latency,scheduling in NR may be decoupled from the slot duration and start atany OFDM symbol and last for as many symbols as needed for atransmission. These partial slot transmissions may be referred to asmini-slot or subslot transmissions.

FIG. 8 illustrates an example configuration of a slot in the time andfrequency domain for an NR carrier. The slot includes resource elements(REs) and resource blocks (RBs). An RE is the smallest physical resourcein NR. An RE spans one OFDM symbol in the time domain by one subcarrierin the frequency domain as shown in FIG. 8 . An RB spans twelveconsecutive REs in the frequency domain as shown in FIG. 8 . An NRcarrier may be limited to a width of 275 RBs or 275×12 = 3300subcarriers. Such a limitation, if used, may limit the NR carrier to 50,100, 200, and 400 MHz for subcarrier spacings of 15, 30, 60, and 120kHz, respectively, where the 400 MHz bandwidth may be set based on a 400MHz per carrier bandwidth limit.

FIG. 8 illustrates a single numerology being used across the entirebandwidth of the NR carrier. In other example configurations, multiplenumerologies may be supported on the same carrier.

NR may support wide carrier bandwidths (e.g., up to 400 MHz for asubcarrier spacing of 120 kHz). Not all UEs may be able to receive thefull carrier bandwidth (e.g., due to hardware limitations). Also,receiving the full carrier bandwidth may be prohibitive in terms of UEpower consumption. In an example, to reduce power consumption and/or forother purposes, a UE may adapt the size of the UE’s receive bandwidthbased on the amount of traffic the UE is scheduled to receive. This isreferred to as bandwidth adaptation.

NR defines bandwidth parts (BWPs) to support UEs not capable ofreceiving the full carrier bandwidth and to support bandwidthadaptation. In an example, a BWP may be defined by a subset ofcontiguous RBs on a carrier. A UE may be configured (e.g., via RRClayer) with one or more downlink BWPs and one or more uplink BWPs perserving cell (e.g., up to four downlink BWPs and up to four uplink BWPsper serving cell). At a given time, one or more of the configured BWPsfor a serving cell may be active. These one or more BWPs may be referredto as active BWPs of the serving cell. When a serving cell is configuredwith a secondary uplink carrier, the serving cell may have one or morefirst active BWPs in the uplink carrier and one or more second activeBWPs in the secondary uplink carrier.

For unpaired spectra, a downlink BWP from a set of configured downlinkBWPs may be linked with an uplink BWP from a set of configured uplinkBWPs if a downlink BWP index of the downlink BWP and an uplink BWP indexof the uplink BWP are the same. For unpaired spectra, a UE may expectthat a center frequency for a downlink BWP is the same as a centerfrequency for an uplink BWP.

For a downlink BWP in a set of configured downlink BWPs on a primarycell (PCell), a base station may configure a UE with one or more controlresource sets (CORESETs) for at least one search space. A search spaceis a set of locations in the time and frequency domains where the UE mayfind control information. The search space may be a UE-specific searchspace or a common search space (potentially usable by a plurality ofUEs). For example, a base station may configure a UE with a commonsearch space, on a PCell or on a primary secondary cell (PSCell), in anactive downlink BWP.

For an uplink BWP in a set of configured uplink BWPs, a BS may configurea UE with one or more resource sets for one or more PUCCH transmissions.A UE may receive downlink receptions (e.g., PDCCH or PDSCH) in adownlink BWP according to a configured numerology (e.g., subcarrierspacing and cyclic prefix duration) for the downlink BWP. The UE maytransmit uplink transmissions (e.g., PUCCH or PUSCH) in an uplink BWPaccording to a configured numerology (e.g., subcarrier spacing andcyclic prefix length for the uplink BWP).

One or more BWP indicator fields may be provided in Downlink ControlInformation (DCI). A value of a BWP indicator field may indicate whichBWP in a set of configured BWPs is an active downlink BWP for one ormore downlink receptions. The value of the one or more BWP indicatorfields may indicate an active uplink BWP for one or more uplinktransmissions.

A base station may semi-statically configure a UE with a defaultdownlink BWP within a set of configured downlink BWPs associated with aPCell. If the base station does not provide the default downlink BWP tothe UE, the default downlink BWP may be an initial active downlink BWP.The UE may determine which BWP is the initial active downlink BWP basedon a CORESET configuration obtained using the PBCH.

A base station may configure a UE with a BWP inactivity timer value fora PCell. The UE may start or restart a BWP inactivity timer at anyappropriate time. For example, the UE may start or restart the BWPinactivity timer (a) when the UE detects a DCI indicating an activedownlink BWP other than a default downlink BWP for a paired spectraoperation; or (b) when a UE detects a DCI indicating an active downlinkBWP or active uplink BWP other than a default downlink BWP or uplink BWPfor an unpaired spectra operation. If the UE does not detect DCI duringan interval of time (e.g., 1 ms or 0.5 ms), the UE may run the BWPinactivity timer toward expiration (for example, increment from zero tothe BWP inactivity timer value, or decrement from the BWP inactivitytimer value to zero). When the BWP inactivity timer expires, the UE mayswitch from the active downlink BWP to the default downlink BWP.

In an example, a base station may semi-statically configure a UE withone or more BWPs. A UE may switch an active BWP from a first BWP to asecond BWP in response to receiving a DCI indicating the second BWP asan active BWP and/or in response to an expiry of the BWP inactivitytimer (e.g., if the second BWP is the default BWP).

Downlink and uplink BWP switching (where BWP switching refers toswitching from a currently active BWP to a not currently active BWP) maybe performed independently in paired spectra. In unpaired spectra,downlink and uplink BWP switching may be performed simultaneously.Switching between configured BWPs may occur based on RRC signaling, DCI,expiration of a BWP inactivity timer, and/or an initiation of randomaccess.

FIG. 9 illustrates an example of bandwidth adaptation using threeconfigured BWPs for an NR carrier. A UE configured with the three BWPsmay switch from one BWP to another BWP at a switching point. In theexample illustrated in FIG. 9 , the BWPs include: a BWP 902 with abandwidth of 40 MHz and a subcarrier spacing of 15 kHz; a BWP 904 with abandwidth of 10 MHz and a subcarrier spacing of 15 kHz; and a BWP 906with a bandwidth of 20 MHz and a subcarrier spacing of 60 kHz. The BWP902 may be an initial active BWP, and the BWP 904 may be a default BWP.The UE may switch between BWPs at switching points. In the example ofFIG. 9 , the UE may switch from the BWP 902 to the BWP 904 at aswitching point 908. The switching at the switching point 908 may occurfor any suitable reason, for example, in response to an expiry of a BWPinactivity timer (indicating switching to the default BWP) and/or inresponse to receiving a DCI indicating BWP 904 as the active BWP. The UEmay switch at a switching point 910 from active BWP 904 to BWP 906 inresponse receiving a DCI indicating BWP 906 as the active BWP. The UEmay switch at a switching point 912 from active BWP 906 to BWP 904 inresponse to an expiry of a BWP inactivity timer and/or in responsereceiving a DCI indicating BWP 904 as the active BWP. The UE may switchat a switching point 914 from active BWP 904 to BWP 902 in responsereceiving a DCI indicating BWP 902 as the active BWP.

If a UE is configured for a secondary cell with a default downlink BWPin a set of configured downlink BWPs and a timer value, UE proceduresfor switching BWPs on a secondary cell may be the same/similar as thoseon a primary cell. For example, the UE may use the timer value and thedefault downlink BWP for the secondary cell in the same/similar manneras the UE would use these values for a primary cell.

To provide for greater data rates, two or more carriers can beaggregated and simultaneously transmitted to/from the same UE usingcarrier aggregation (CA). The aggregated carriers in CA may be referredto as component carriers (CCs). When CA is used, there are a number ofserving cells for the UE, one for a CC. The CCs may have threeconfigurations in the frequency domain.

FIG. 10A illustrates the three CA configurations with two CCs. In theintraband, contiguous configuration 1002, the two CCs are aggregated inthe same frequency band (frequency band A) and are located directlyadjacent to each other within the frequency band. In the intraband,non-contiguous configuration 1004, the two CCs are aggregated in thesame frequency band (frequency band A) and are separated in thefrequency band by a gap. In the interband configuration 1006, the twoCCs are located in frequency bands (frequency band A and frequency bandB).

In an example, up to 32 CCs may be aggregated. The aggregated CCs mayhave the same or different bandwidths, subcarrier spacing, and/orduplexing schemes (TDD or FDD). A serving cell for a UE using CA mayhave a downlink CC. For FDD, one or more uplink CCs may be optionallyconfigured for a serving cell. The ability to aggregate more downlinkcarriers than uplink carriers may be useful, for example, when the UEhas more data traffic in the downlink than in the uplink.

When CA is used, one of the aggregated cells for a UE may be referred toas a primary cell (PCell). The PCell may be the serving cell that the UEinitially connects to at RRC connection establishment, reestablishment,and/or handover. The PCell may provide the UE with NAS mobilityinformation and the security input. UEs may have different PCells. Inthe downlink, the carrier corresponding to the PCell may be referred toas the downlink primary CC (DL PCC). In the uplink, the carriercorresponding to the PCell may be referred to as the uplink primary CC(UL PCC). The other aggregated cells for the UE may be referred to assecondary cells (SCells). In an example, the SCells may be configuredafter the PCell is configured for the UE. For example, an SCell may beconfigured through an RRC Connection Reconfiguration procedure. In thedownlink, the carrier corresponding to an SCell may be referred to as adownlink secondary CC (DL SCC). In the uplink, the carrier correspondingto the SCell may be referred to as the uplink secondary CC (UL SCC).

Configured SCells for a UE may be activated and deactivated based on,for example, traffic and channel conditions. Deactivation of an SCellmay mean that PDCCH and PDSCH reception on the SCell is stopped andPUSCH, SRS, and CQI transmissions on the SCell are stopped. ConfiguredSCells may be activated and deactivated using a MAC CE with respect toFIG. 4B. For example, a MAC CE may use a bitmap (e.g., one bit perSCell) to indicate which SCells (e.g., in a subset of configured SCells)for the UE are activated or deactivated. Configured SCells may bedeactivated in response to an expiration of an SCell deactivation timer(e.g., one SCell deactivation timer per SCell).

Downlink control information, such as scheduling assignments andscheduling grants, for a cell may be transmitted on the cellcorresponding to the assignments and grants, which is known asself-scheduling. The DCI for the cell may be transmitted on anothercell, which is known as cross-carrier scheduling. Uplink controlinformation (e.g., HARQ acknowledgments and channel state feedback, suchas CQI, PMI, and/or RI) for aggregated cells may be transmitted on thePUCCH of the PCell. For a larger number of aggregated downlink CCs, thePUCCH of the PCell may become overloaded. Cells may be divided intomultiple PUCCH groups.

FIG. 10B illustrates an example of how aggregated cells may beconfigured into one or more PUCCH groups. A PUCCH group 1010 and a PUCCHgroup 1050 may include one or more downlink CCs, respectively. In theexample of FIG. 10B, the PUCCH group 1010 includes three downlink CCs— aPCell 1011, an SCell 1012, and an SCell 1013. The PUCCH group 1050includes three downlink CCs in the present example: a PCell 1051, anSCell 1052, and an SCell 1053. One or more uplink CCs may be configuredas a PCell 1021, an SCell 1022, and an SCell 1023. One or more otheruplink CCs may be configured as a primary Scell (PSCell) 1061, an SCell1062, and an SCell 1063. Uplink control information (UCI) related to thedownlink CCs of the PUCCH group 1010, shown as UCI 1031, UCI 1032, andUCI 1033, may be transmitted in the uplink of the PCell 1021. Uplinkcontrol information (UCI) related to the downlink CCs of the PUCCH group1050, shown as UCI 1071, UCI 1072, and UCI 1073, may be transmitted inthe uplink of the PSCell 1061. In an example, if the aggregated cellsdepicted in FIG. 10B were not divided into the PUCCH group 1010 and thePUCCH group 1050, a single uplink PCell to transmit UCI relating to thedownlink CCs, and the PCell may become overloaded. By dividingtransmissions of UCI between the PCell 1021 and the PSCell 1061,overloading may be prevented.

A cell, comprising a downlink carrier and optionally an uplink carrier,may be assigned with a physical cell ID and a cell index. The physicalcell ID or the cell index may identify a downlink carrier and/or anuplink carrier of the cell, for example, depending on the context inwhich the physical cell ID is used. A physical cell ID may be determinedusing a synchronization signal transmitted on a downlink componentcarrier. A cell index may be determined using RRC messages. In thedisclosure, a physical cell ID may be referred to as a carrier ID, and acell index may be referred to as a carrier index. For example, when thedisclosure refers to a first physical cell ID for a first downlinkcarrier, the disclosure may mean the first physical cell ID is for acell comprising the first downlink carrier. The same/similar concept mayapply to, for example, a carrier activation. When the disclosureindicates that a first carrier is activated, the specification may meanthat a cell comprising the first carrier is activated.

In CA, a multi-carrier nature of a PHY may be exposed to a MAC. In anexample, a HARQ entity may operate on a serving cell. A transport blockmay be generated per assignment/grant per serving cell. A transportblock and potential HARQ retransmissions of the transport block may bemapped to a serving cell.

In the downlink, a base station may transmit (e.g., unicast, multicast,and/or broadcast) one or more Reference Signals (RSs) to a UE (e.g.,PSS, SSS, CSI-RS, DMRS, and/or PT-RS, as shown in FIG. 5A). In theuplink, the UE may transmit one or more RSs to the base station (e.g.,DMRS, PT-RS, and/or SRS, as shown in FIG. 5B). The PSS and the SSS maybe transmitted by the base station and used by the UE to synchronize theUE to the base station. The PSS and the SSS may be provided in asynchronization signal (SS) / physical broadcast channel (PBCH) blockthat includes the PSS, the SSS, and the PBCH. The base station mayperiodically transmit a burst of SS/PBCH blocks.

FIG. 11A illustrates an example of an SS/PBCH block’s structure andlocation. A burst of SS/PBCH blocks may include one or more SS/PBCHblocks (e.g., 4 SS/PBCH blocks, as shown in FIG. 11A). Bursts may betransmitted periodically (e.g., every 2 frames or 20 ms). A burst may berestricted to a half-frame (e.g., a first half-frame having a durationof 5 ms). It will be understood that FIG. 11A is an example, and thatthese parameters (number of SS/PBCH blocks per burst, periodicity ofbursts, position of burst within the frame) may be configured based on,for example: a carrier frequency of a cell in which the SS/PBCH block istransmitted; a numerology or subcarrier spacing of the cell; aconfiguration by the network (e.g., using RRC signaling); or any othersuitable factor. In an example, the UE may assume a subcarrier spacingfor the SS/PBCH block based on the carrier frequency being monitored,unless the radio network configured the UE to assume a differentsubcarrier spacing.

The SS/PBCH block may span one or more OFDM symbols in the time domain(e.g., 4 OFDM symbols, as shown in the example of FIG. 11A) and may spanone or more subcarriers in the frequency domain (e.g., 240 contiguoussubcarriers). The PSS, the SSS, and the PBCH may have a common centerfrequency. The PSS may be transmitted first and may span, for example, 1OFDM symbol and 127 subcarriers. The SSS may be transmitted after thePSS (e.g., two symbols later) and may span 1 OFDM symbol and 127subcarriers. The PBCH may be transmitted after the PSS (e.g., across thenext 3 OFDM symbols) and may span 240 subcarriers.

The location of the SS/PBCH block in the time and frequency domains maynot be known to the UE (e.g., if the UE is searching for the cell). Tofind and select the cell, the UE may monitor a carrier for the PSS. Forexample, the UE may monitor a frequency location within the carrier. Ifthe PSS is not found after a certain duration (e.g., 20 ms), the UE maysearch for the PSS at a different frequency location within the carrier,as indicated by a synchronization raster. If the PSS is found at alocation in the time and frequency domains, the UE may determine, basedon a known structure of the SS/PBCH block, the locations of the SSS andthe PBCH, respectively. The SS/PBCH block may be a cell-defining SSblock (CD-SSB). In an example, a primary cell may be associated with aCD-SSB. The CD-SSB may be located on a synchronization raster. In anexample, a cell selection/search and/or reselection may be based on theCD-SSB.

The SS/PBCH block may be used by the UE to determine one or moreparameters of the cell. For example, the UE may determine a physicalcell identifier (PCI) of the cell based on the sequences of the PSS andthe SSS, respectively. The UE may determine a location of a frameboundary of the cell based on the location of the SS/PBCH block. Forexample, the SS/PBCH block may indicate that it has been transmitted inaccordance with a transmission pattern, wherein a SS/PBCH block in thetransmission pattern is a known distance from the frame boundary.

The PBCH may use a QPSK modulation and may use forward error correction(FEC). The FEC may use polar coding. One or more symbols spanned by thePBCH may carry one or more DMRSs for demodulation of the PBCH. The PBCHmay include an indication of a current system frame number (SFN) of thecell and/or a SS/PBCH block timing index. These parameters mayfacilitate time synchronization of the UE to the base station. The PBCHmay include a master information block (MIB) used to provide the UE withone or more parameters. The MIB may be used by the UE to locateremaining minimum system information (RMSI) associated with the cell.The RMSI may include a System Information Block Type 1 (SIB1). The SIB1may contain information needed by the UE to access the cell. The UE mayuse one or more parameters of the MIB to monitor PDCCH, which may beused to schedule PDSCH. The PDSCH may include the SIB1. The SIB1 may bedecoded using parameters provided in the MIB. The PBCH may indicate anabsence of SIB1. Based on the PBCH indicating the absence of SIB1, theUE may be pointed to a frequency. The UE may search for an SS/PBCH blockat the frequency to which the UE is pointed.

The UE may assume that one or more SS/PBCH blocks transmitted with asame SS/PBCH block index are quasi co-located (QCLed) (e.g., having thesame/similar Doppler spread, Doppler shift, average gain, average delay,and/or spatial Rx parameters). The UE may not assume QCL for SS/PBCHblock transmissions having different SS/PBCH block indices.

SS/PBCH blocks (e.g., those within a half-frame) may be transmitted inspatial directions (e.g., using different beams that span a coveragearea of the cell). In an example, a first SS/PBCH block may betransmitted in a first spatial direction using a first beam, and asecond SS/PBCH block may be transmitted in a second spatial directionusing a second beam.

In an example, within a frequency span of a carrier, a base station maytransmit a plurality of SS/PBCH blocks. In an example, a first PCI of afirst SS/PBCH block of the plurality of SS/PBCH blocks may be differentfrom a second PCI of a second SS/PBCH block of the plurality of SS/PBCHblocks. The PCIs of SS/PBCH blocks transmitted in different frequencylocations may be different or the same.

The CSI-RS may be transmitted by the base station and used by the UE toacquire channel state information (CSI). The base station may configurethe UE with one or more CSI-RSs for channel estimation or any othersuitable purpose. The base station may configure a UE with one or moreof the same/similar CSI-RSs. The UE may measure the one or more CSI-RSs.The UE may estimate a downlink channel state and/or generate a CSIreport based on the measuring of the one or more downlink CSI-RSs. TheUE may provide the CSI report to the base station. The base station mayuse feedback provided by the UE (e.g., the estimated downlink channelstate) to perform link adaptation.

The base station may semi-statically configure the UE with one or moreCSI-RS resource sets. A CSI-RS resource may be associated with alocation in the time and frequency domains and a periodicity. The basestation may selectively activate and/or deactivate a CSI-RS resource.The base station may indicate to the UE that a CSI-RS resource in theCSI-RS resource set is activated and/or deactivated.

The base station may configure the UE to report CSI measurements. Thebase station may configure the UE to provide CSI reports periodically,aperiodically, or semi-persistently. For periodic CSI reporting, the UEmay be configured with a timing and/or periodicity of a plurality of CSIreports. For aperiodic CSI reporting, the base station may request a CSIreport. For example, the base station may command the UE to measure aconfigured CSI-RS resource and provide a CSI report relating to themeasurements. For semi-persistent CSI reporting, the base station mayconfigure the UE to transmit periodically, and selectively activate ordeactivate the periodic reporting. The base station may configure the UEwith a CSI-RS resource set and CSI reports using RRC signaling.

The CSI-RS configuration may comprise one or more parameters indicating,for example, up to 32 antenna ports. The UE may be configured to employthe same OFDM symbols for a downlink CSI-RS and a control resource set(CORESET) when the downlink CSI-RS and CORESET are spatially QCLed andresource elements associated with the downlink CSI-RS are outside of thephysical resource blocks (PRBs) configured for the CORESET. The UE maybe configured to employ the same OFDM symbols for downlink CSI-RS andSS/PBCH blocks when the downlink CSI-RS and SS/PBCH blocks are spatiallyQCLed and resource elements associated with the downlink CSI-RS areoutside of PRBs configured for the SS/PBCH blocks.

Downlink DMRSs may be transmitted by a base station and used by a UE forchannel estimation. For example, the downlink DMRS may be used forcoherent demodulation of one or more downlink physical channels (e.g.,PDSCH). An NR network may support one or more variable and/orconfigurable DMRS patterns for data demodulation. At least one downlinkDMRS configuration may support a front-loaded DMRS pattern. Afront-loaded DMRS may be mapped over one or more OFDM symbols (e.g., oneor two adjacent OFDM symbols). A base station may semi-staticallyconfigure the UE with a number (e.g. a maximum number) of front-loadedDMRS symbols for PDSCH. A DMRS configuration may support one or moreDMRS ports. For example, for single user-MIMO, a DMRS configuration maysupport up to eight orthogonal downlink DMRS ports per UE. Formultiuser-MIMO, a DMRS configuration may support up to 4 orthogonaldownlink DMRS ports per UE. A radio network may support (e.g., at leastfor CP-OFDM) a common DMRS structure for downlink and uplink, wherein aDMRS location, a DMRS pattern, and/or a scrambling sequence may be thesame or different. The base station may transmit a downlink DMRS and acorresponding PDSCH using the same precoding matrix. The UE may use theone or more downlink DMRSs for coherent demodulation/channel estimationof the PDSCH.

In an example, a transmitter (e.g., a base station) may use a precodermatrices for a part of a transmission bandwidth. For example, thetransmitter may use a first precoder matrix for a first bandwidth and asecond precoder matrix for a second bandwidth. The first precoder matrixand the second precoder matrix may be different based on the firstbandwidth being different from the second bandwidth. The UE may assumethat a same precoding matrix is used across a set of PRBs. The set ofPRBs may be denoted as a precoding resource block group (PRG).

A PDSCH may comprise one or more layers. The UE may assume that at leastone symbol with DMRS is present on a layer of the one or more layers ofthe PDSCH. A higher layer may configure up to 3 DMRSs for the PDSCH.

Downlink PT-RS may be transmitted by a base station and used by a UE forphase-noise compensation. Whether a downlink PT-RS is present or not maydepend on an RRC configuration. The presence and/or pattern of thedownlink PT-RS may be configured on a UE-specific basis using acombination of RRC signaling and/or an association with one or moreparameters employed for other purposes (e.g., modulation and codingscheme (MCS)), which may be indicated by DCI. When configured, a dynamicpresence of a downlink PT-RS may be associated with one or more DCIparameters comprising at least MCS. An NR network may support aplurality of PT-RS densities defined in the time and/or frequencydomains. When present, a frequency domain density may be associated withat least one configuration of a scheduled bandwidth. The UE may assume asame precoding for a DMRS port and a PT-RS port. A number of PT-RS portsmay be fewer than a number of DMRS ports in a scheduled resource.Downlink PT-RS may be confined in the scheduled time/frequency durationfor the UE. Downlink PT-RS may be transmitted on symbols to facilitatephase tracking at the receiver.

The UE may transmit an uplink DMRS to a base station for channelestimation. For example, the base station may use the uplink DMRS forcoherent demodulation of one or more uplink physical channels. Forexample, the UE may transmit an uplink DMRS with a PUSCH and/or a PUCCH.The uplink DM-RS may span a range of frequencies that is similar to arange of frequencies associated with the corresponding physical channel.The base station may configure the UE with one or more uplink DMRSconfigurations. At least one DMRS configuration may support afront-loaded DMRS pattern. The front-loaded DMRS may be mapped over oneor more OFDM symbols (e.g., one or two adjacent OFDM symbols). One ormore uplink DMRSs may be configured to transmit at one or more symbolsof a PUSCH and/or a PUCCH. The base station may semi-staticallyconfigure the UE with a number (e.g. maximum number) of front-loadedDMRS symbols for the PUSCH and/or the PUCCH, which the UE may use toschedule a single-symbol DMRS and/or a double-symbol DMRS. An NR networkmay support (e.g., for cyclic prefix orthogonal frequency divisionmultiplexing (CP-OFDM)) a common DMRS structure for downlink and uplink,wherein a DMRS location, a DMRS pattern, and/or a scrambling sequencefor the DMRS may be the same or different.

A PUSCH may comprise one or more layers, and the UE may transmit atleast one symbol with DMRS present on a layer of the one or more layersof the PUSCH. In an example, a higher layer may configure up to threeDMRSs for the PUSCH.

Uplink PT-RS (which may be used by a base station for phase trackingand/or phase-noise compensation) may or may not be present depending onan RRC configuration of the UE. The presence and/or pattern of uplinkPT-RS may be configured on a UE-specific basis by a combination of RRCsignaling and/or one or more parameters employed for other purposes(e.g., Modulation and Coding Scheme (MCS)), which may be indicated byDCI. When configured, a dynamic presence of uplink PT-RS may beassociated with one or more DCI parameters comprising at least MCS. Aradio network may support a plurality of uplink PT-RS densities definedin time/frequency domain. When present, a frequency domain density maybe associated with at least one configuration of a scheduled bandwidth.The UE may assume a same precoding for a DMRS port and a PT-RS port. Anumber of PT-RS ports may be fewer than a number of DMRS ports in ascheduled resource. For example, uplink PT-RS may be confined in thescheduled time/frequency duration for the UE.

SRS may be transmitted by a UE to a base station for channel stateestimation to support uplink channel dependent scheduling and/or linkadaptation. SRS transmitted by the UE may allow a base station toestimate an uplink channel state at one or more frequencies. A schedulerat the base station may employ the estimated uplink channel state toassign one or more resource blocks for an uplink PUSCH transmission fromthe UE. The base station may semi-statically configure the UE with oneor more SRS resource sets. For an SRS resource set, the base station mayconfigure the UE with one or more SRS resources. An SRS resource setapplicability may be configured by a higher layer (e.g., RRC) parameter.For example, when a higher layer parameter indicates beam management, anSRS resource in a SRS resource set of the one or more SRS resource sets(e.g., with the same/similar time domain behavior, periodic, aperiodic,and/or the like) may be transmitted at a time instant (e.g.,simultaneously). The UE may transmit one or more SRS resources in SRSresource sets. An NR network may support aperiodic, periodic and/orsemi-persistent SRS transmissions. The UE may transmit SRS resourcesbased on one or more trigger types, wherein the one or more triggertypes may comprise higher layer signaling (e.g., RRC) and/or one or moreDCI formats. In an example, at least one DCI format may be employed forthe UE to select at least one of one or more configured SRS resourcesets. An SRS trigger type 0 may refer to an SRS triggered based on ahigher layer signaling. An SRS trigger type 1 may refer to an SRStriggered based on one or more DCI formats. In an example, when PUSCHand SRS are transmitted in a same slot, the UE may be configured totransmit SRS after a transmission of a PUSCH and a corresponding uplinkDMRS.

The base station may semi-statically configure the UE with one or moreSRS configuration parameters indicating at least one of following: a SRSresource configuration identifier; a number of SRS ports; time domainbehavior of an SRS resource configuration (e.g., an indication ofperiodic, semi-persistent, or aperiodic SRS); slot, mini-slot, and/orsubframe level periodicity; offset for a periodic and/or an aperiodicSRS resource; a number of OFDM symbols in an SRS resource; a startingOFDM symbol of an SRS resource; an SRS bandwidth; a frequency hoppingbandwidth; a cyclic shift; and/or an SRS sequence ID.

An antenna port is defined such that the channel over which a symbol onthe antenna port is conveyed can be inferred from the channel over whichanother symbol on the same antenna port is conveyed. If a first symboland a second symbol are transmitted on the same antenna port, thereceiver may infer the channel (e.g., fading gain, multipath delay,and/or the like) for conveying the second symbol on the antenna port,from the channel for conveying the first symbol on the antenna port. Afirst antenna port and a second antenna port may be referred to as quasico-located (QCLed) if one or more large-scale properties of the channelover which a first symbol on the first antenna port is conveyed may beinferred from the channel over which a second symbol on a second antennaport is conveyed. The one or more large-scale properties may comprise atleast one of: a delay spread; a Doppler spread; a Doppler shift; anaverage gain; an average delay; and/or spatial Receiving (Rx)parameters.

Channels that use beamforming require beam management. Beam managementmay comprise beam measurement, beam selection, and beam indication. Abeam may be associated with one or more reference signals. For example,a beam may be identified by one or more beamformed reference signals.The UE may perform downlink beam measurement based on downlink referencesignals (e.g., a channel state information reference signal (CSI-RS))and generate a beam measurement report. The UE may perform the downlinkbeam measurement procedure after an RRC connection is set up with a basestation.

FIG. 11B illustrates an example of channel state information referencesignals (CSI-RSs) that are mapped in the time and frequency domains. Asquare shown in FIG. 11B may span a resource block (RB) within abandwidth of a cell. A base station may transmit one or more RRCmessages comprising CSI-RS resource configuration parameters indicatingone or more CSI-RSs. One or more of the following parameters may beconfigured by higher layer signaling (e.g., RRC and/or MAC signaling)for a CSI-RS resource configuration: a CSI-RS resource configurationidentity, a number of CSI-RS ports, a CSI-RS configuration (e.g., symboland resource element (RE) locations in a subframe), a CSI-RS subframeconfiguration (e.g., subframe location, offset, and periodicity in aradio frame), a CSI-RS power parameter, a CSI-RS sequence parameter, acode division multiplexing (CDM) type parameter, a frequency density, atransmission comb, quasi co-location (QCL) parameters (e.g.,QCL-scramblingidentity, crs-portscount, mbsfn-subframeconfiglist,csi-rs-configZPid, qcl-csi-rs-configNZPid), and/or other radio resourceparameters.

The three beams illustrated in FIG. 11B may be configured for a UE in aUE-specific configuration. Three beams are illustrated in FIG. 11B (beam#1, beam #2, and beam #3), more or fewer beams may be configured. Beam#1 may be allocated with CSI-RS 1101 that may be transmitted in one ormore subcarriers in an RB of a first symbol. Beam #2 may be allocatedwith CSI-RS 1102 that may be transmitted in one or more subcarriers inan RB of a second symbol. Beam #3 may be allocated with CSI-RS 1103 thatmay be transmitted in one or more subcarriers in an RB of a thirdsymbol. By using frequency division multiplexing (FDM), a base stationmay use other subcarriers in a same RB (for example, those that are notused to transmit CSI-RS 1101) to transmit another CSI-RS associated witha beam for another UE. By using time domain multiplexing (TDM), beamsused for the UE may be configured such that beams for the UE use symbolsfrom beams of other UEs.

CSI-RSs such as those illustrated in FIG. 11B (e.g., CSI-RS 1101, 1102,1103) may be transmitted by the base station and used by the UE for oneor more measurements. For example, the UE may measure a reference signalreceived power (RSRP) of configured CSI-RS resources. The base stationmay configure the UE with a reporting configuration and the UE mayreport the RSRP measurements to a network (for example, via one or morebase stations) based on the reporting configuration. In an example, thebase station may determine, based on the reported measurement results,one or more transmission configuration indication (TCI) statescomprising a number of reference signals. In an example, the basestation may indicate one or more TCI states to the UE (e.g., via RRCsignaling, a MAC CE, and/or a DCI). The UE may receive a downlinktransmission with a receive (Rx) beam determined based on the one ormore TCI states. In an example, the UE may or may not have a capabilityof beam correspondence. If the UE has the capability of beamcorrespondence, the UE may determine a spatial domain filter of atransmit (Tx) beam based on a spatial domain filter of the correspondingRx beam. If the UE does not have the capability of beam correspondence,the UE may perform an uplink beam selection procedure to determine thespatial domain filter of the Tx beam. The UE may perform the uplink beamselection procedure based on one or more sounding reference signal (SRS)resources configured to the UE by the base station. The base station mayselect and indicate uplink beams for the UE based on measurements of theone or more SRS resources transmitted by the UE.

In a beam management procedure, a UE may assess (e.g., measure) achannel quality of one or more beam pair links, a beam pair linkcomprising a transmitting beam transmitted by a base station and areceiving beam received by the UE. Based on the assessment, the UE maytransmit a beam measurement report indicating one or more beam pairquality parameters comprising, e.g., one or more beam identifications(e.g., a beam index, a reference signal index, or the like), RSRP, aprecoding matrix indicator (PMI), a channel quality indicator (CQI),and/or a rank indicator (RI).

FIG. 12A illustrates examples of three downlink beam managementprocedures: P1, P2, and P3. Procedure P1 may enable a UE measurement ontransmit (Tx) beams of a transmission reception point (TRP) (or multipleTRPs), e.g., to support a selection of one or more base station Tx beamsand/or UE Rx beams (shown as ovals in the top row and bottom row,respectively, of P1). Beamforming at a TRP may comprise a Tx beam sweepfor a set of beams (shown, in the top rows of P1 and P2, as ovalsrotated in a counter-clockwise direction indicated by the dashed arrow).Beamforming at a UE may comprise an Rx beam sweep for a set of beams(shown, in the bottom rows of P1 and P3, as ovals rotated in a clockwisedirection indicated by the dashed arrow). Procedure P2 may be used toenable a UE measurement on Tx beams of a TRP (shown, in the top row ofP2, as ovals rotated in a counter-clockwise direction indicated by thedashed arrow). The UE and/or the base station may perform procedure P2using a smaller set of beams than is used in procedure P1, or usingnarrower beams than the beams used in procedure P1. This may be referredto as beam refinement. The UE may perform procedure P3 for Rx beamdetermination by using the same Tx beam at the base station and sweepingan Rx beam at the UE.

FIG. 12B illustrates examples of three uplink beam managementprocedures: U1, U2, and U3. Procedure U1 may be used to enable a basestation to perform a measurement on Tx beams of a UE, e.g., to support aselection of one or more UE Tx beams and/or base station Rx beams (shownas ovals in the top row and bottom row, respectively, of U1).Beamforming at the UE may include, e.g., a Tx beam sweep from a set ofbeams (shown in the bottom rows of U1 and U3 as ovals rotated in aclockwise direction indicated by the dashed arrow). Beamforming at thebase station may include, e.g., an Rx beam sweep from a set of beams(shown, in the top rows of U1 and U2, as ovals rotated in acounter-clockwise direction indicated by the dashed arrow). Procedure U2may be used to enable the base station to adjust its Rx beam when the UEuses a fixed Tx beam. The UE and/or the base station may performprocedure U2 using a smaller set of beams than is used in procedure P1,or using narrower beams than the beams used in procedure P1. This may bereferred to as beam refinement The UE may perform procedure U3 to adjustits Tx beam when the base station uses a fixed Rx beam.

A UE may initiate a beam failure recovery (BFR) procedure based ondetecting a beam failure. The UE may transmit a BFR request (e.g., apreamble, a UCI, an SR, a MAC CE, and/or the like) based on theinitiating of the BFR procedure. The UE may detect the beam failurebased on a determination that a quality of beam pair link(s) of anassociated control channel is unsatisfactory (e.g., having an error ratehigher than an error rate threshold, a received signal power lower thana received signal power threshold, an expiration of a timer, and/or thelike).

The UE may measure a quality of a beam pair link using one or morereference signals (RSs) comprising one or more SS/PBCH blocks, one ormore CSI-RS resources, and/or one or more demodulation reference signals(DMRSs). A quality of the beam pair link may be based on one or more ofa block error rate (BLER), an RSRP value, a signal to interference plusnoise ratio (SINR) value, a reference signal received quality (RSRQ)value, and/or a CSI value measured on RS resources. The base station mayindicate that an RS resource is quasi co-located (QCLed) with one ormore DM-RSs of a channel (e.g., a control channel, a shared datachannel, and/or the like). The RS resource and the one or more DMRSs ofthe channel may be QCLed when the channel characteristics (e.g., Dopplershift, Doppler spread, average delay, delay spread, spatial Rxparameter, fading, and/or the like) from a transmission via the RSresource to the UE are similar or the same as the channelcharacteristics from a transmission via the channel to the UE.

A network (e.g., a gNB and/or an ng-eNB of a network) and/or the UE mayinitiate a random access procedure. A UE in an RRC_IDLE state and/or anRRC_INACTIVE state may initiate the random access procedure to request aconnection setup to a network. The UE may initiate the random accessprocedure from an RRC_CONNECTED state. The UE may initiate the randomaccess procedure to request uplink resources (e.g., for uplinktransmission of an SR when there is no PUCCH resource available) and/oracquire uplink timing (e.g., when uplink synchronization status isnon-synchronized). The UE may initiate the random access procedure torequest one or more system information blocks (SIBs) (e.g., other systeminformation such as SIB2, SIB3, and/or the like). The UE may initiatethe random access procedure for a beam failure recovery request. Anetwork may initiate a random access procedure for a handover and/or forestablishing time alignment for an SCell addition.

FIG. 13A illustrates a four-step contention-based random accessprocedure. Prior to initiation of the procedure, a base station maytransmit a configuration message 1310 to the UE. The procedureillustrated in FIG. 13A comprises transmission of four messages: a Msg 11311, a Msg 2 1312, a Msg 3 1313, and a Msg 4 1314. The Msg 1 1311 mayinclude and/or be referred to as a preamble (or a random accesspreamble). The Msg 2 1312 may include and/or be referred to as a randomaccess response (RAR).

The configuration message 1310 may be transmitted, for example, usingone or more RRC messages. The one or more RRC messages may indicate oneor more random access channel (RACH) parameters to the UE. The one ormore RACH parameters may comprise at least one of following: generalparameters for one or more random access procedures (e.g.,RACH-configGeneral); cell-specific parameters (e.g., RACH-ConfigCommon);and/or dedicated parameters (e.g., RACH-configDedicated). The basestation may broadcast or multicast the one or more RRC messages to oneor more UEs. The one or more RRC messages may be UE-specific (e.g.,dedicated RRC messages transmitted to a UE in an RRC_CONNECTED stateand/or in an RRC_INACTIVE state). The UE may determine, based on the oneor more RACH parameters, a time-frequency resource and/or an uplinktransmit power for transmission of the Msg 1 1311 and/or the Msg 3 1313.Based on the one or more RACH parameters, the UE may determine areception timing and a downlink channel for receiving the Msg 2 1312 andthe Msg 4 1314.

The one or more RACH parameters provided in the configuration message1310 may indicate one or more Physical RACH (PRACH) occasions availablefor transmission of the Msg 1 1311. The one or more PRACH occasions maybe predefined. The one or more RACH parameters may indicate one or moreavailable sets of one or more PRACH occasions (e.g., prach-ConfigIndex).The one or more RACH parameters may indicate an association between (a)one or more PRACH occasions and (b) one or more reference signals. Theone or more RACH parameters may indicate an association between (a) oneor more preambles and (b) one or more reference signals. The one or morereference signals may be SS/PBCH blocks and/or CSI-RSs. For example, theone or more RACH parameters may indicate a number of SS/PBCH blocksmapped to a PRACH occasion and/or a number of preambles mapped to aSS/PBCH blocks.

The one or more RACH parameters provided in the configuration message1310 may be used to determine an uplink transmit power of Msg 1 1311and/or Msg 3 1313. For example, the one or more RACH parameters mayindicate a reference power for a preamble transmission (e.g., a receivedtarget power and/or an initial power of the preamble transmission).There may be one or more power offsets indicated by the one or more RACHparameters. For example, the one or more RACH parameters may indicate: apower ramping step; a power offset between SSB and CSI-RS; a poweroffset between transmissions of the Msg 1 1311 and the Msg 3 1313;and/or a power offset value between preamble groups. The one or moreRACH parameters may indicate one or more thresholds based on which theUE may determine at least one reference signal (e.g., an SSB and/orCSI-RS) and/or an uplink carrier (e.g., a normal uplink (NUL) carrierand/or a supplemental uplink (SUL) carrier).

The Msg 1 1311 may include one or more preamble transmissions (e.g., apreamble transmission and one or more preamble retransmissions). An RRCmessage may be used to configure one or more preamble groups (e.g.,group A and/or group B). A preamble group may comprise one or morepreambles. The UE may determine the preamble group based on a pathlossmeasurement and/or a size of the Msg 3 1313. The UE may measure an RSRPof one or more reference signals (e.g., SSBs and/or CSI-RSs) anddetermine at least one reference signal having an RSRP above an RSRPthreshold (e.g., rsrp-ThresholdSSB and/or rsrp-ThresholdCSI-RS). The UEmay select at least one preamble associated with the one or morereference signals and/or a selected preamble group, for example, if theassociation between the one or more preambles and the at least onereference signal is configured by an RRC message.

The UE may determine the preamble based on the one or more RACHparameters provided in the configuration message 1310. For example, theUE may determine the preamble based on a pathloss measurement, an RSRPmeasurement, and/or a size of the Msg 3 1313. As another example, theone or more RACH parameters may indicate: a preamble format; a maximumnumber of preamble transmissions; and/or one or more thresholds fordetermining one or more preamble groups (e.g., group A and group B). Abase station may use the one or more RACH parameters to configure the UEwith an association between one or more preambles and one or morereference signals (e.g., SSBs and/or CSI-RSs). If the association isconfigured, the UE may determine the preamble to include in Msg 1 1311based on the association. The Msg 1 1311 may be transmitted to the basestation via one or more PRACH occasions. The UE may use one or morereference signals (e.g., SSBs and/or CSI-RSs) for selection of thepreamble and for determining of the PRACH occasion. One or more RACHparameters (e.g., ra-ssb-OccasionMskIndex and/or ra-OccasionList) mayindicate an association between the PRACH occasions and the one or morereference signals.

The UE may perform a preamble retransmission if no response is receivedfollowing a preamble transmission. The UE may increase an uplinktransmit power for the preamble retransmission. The UE may select aninitial preamble transmit power based on a pathloss measurement and/or atarget received preamble power configured by the network. The UE maydetermine to retransmit a preamble and may ramp up the uplink transmitpower. The UE may receive one or more RACH parameters (e.g.,PREAMBLE_POWER_RAMPING_STEP) indicating a ramping step for the preambleretransmission. The ramping step may be an amount of incrementalincrease in uplink transmit power for a retransmission. The UE may rampup the uplink transmit power if the UE determines a reference signal(e.g., SSB and/or CSI-RS) that is the same as a previous preambletransmission. The UE may count a number of preamble transmissions and/orretransmissions (e.g., PREAMBLE_TRANSMISSION_COUNTER). The UE maydetermine that a random access procedure completed unsuccessfully, forexample, if the number of preamble transmissions exceeds a thresholdconfigured by the one or more RACH parameters (e.g., preambleTransMax).

The Msg 2 1312 received by the UE may include an RAR. In some scenarios,the Msg 2 1312 may include multiple RARs corresponding to multiple UEs.The Msg 2 1312 may be received after or in response to the transmittingof the Msg 1 1311. The Msg 2 1312 may be scheduled on the DL-SCH andindicated on a PDCCH using a random access RNTI (RA-RNTI). The Msg 21312 may indicate that the Msg 1 1311 was received by the base station.The Msg 2 1312 may include a time-alignment command that may be used bythe UE to adjust the UE’s transmission timing, a scheduling grant fortransmission of the Msg 3 1313, and/or a Temporary Cell RNTI (TC-RNTI).After transmitting a preamble, the UE may start a time window (e.g.,ra-ResponseWindow) to monitor a PDCCH for the Msg 2 1312. The UE maydetermine when to start the time window based on a PRACH occasion thatthe UE uses to transmit the preamble. For example, the UE may start thetime window one or more symbols after a last symbol of the preamble(e.g., at a first PDCCH occasion from an end of a preambletransmission). The one or more symbols may be determined based on anumerology. The PDCCH may be in a common search space (e.g., aType1-PDCCH common search space) configured by an RRC message. The UEmay identify the RAR based on a Radio Network Temporary Identifier(RNTI). RNTIs may be used depending on one or more events initiating therandom access procedure. The UE may use random access RNTI (RA-RNTI).The RA-RNTI may be associated with PRACH occasions in which the UEtransmits a preamble. For example, the UE may determine the RA-RNTIbased on: an OFDM symbol index; a slot index; a frequency domain index;and/or a UL carrier indicator of the PRACH occasions. An example ofRA-RNTI may be as follows:

RA-RNTI= 1 + s_id + 14 × t_id + 14 × 80 × f_id + 14 × 80 × 8 ×ul_carrier_id,

where s_id may be an index of a first OFDM symbol of the PRACH occasion(e.g., 0 ≤ s_id < 14), t_id may be an index of a first slot of the PRACHoccasion in a system frame (e.g., 0 ≤ t_id < 80), f_id may be an indexof the PRACH occasion in the frequency domain (e.g., 0 ≤ f_id < 8), andul_carrier_id may be a UL carrier used for a preamble transmission(e.g., 0 for an NUL carrier, and 1 for an SUL carrier).

The UE may transmit the Msg 3 1313 in response to a successful receptionof the Msg 2 1312 (e.g., using resources identified in the Msg 2 1312).The Msg 3 1313 may be used for contention resolution in, for example,the contention-based random access procedure illustrated in FIG. 13A. Insome scenarios, a plurality of UEs may transmit a same preamble to abase station and the base station may provide an RAR that corresponds toa UE. Collisions may occur if the plurality of UEs interpret the RAR ascorresponding to themselves. Contention resolution (e.g., using the Msg3 1313 and the Msg 4 1314) may be used to increase the likelihood thatthe UE does not incorrectly use an identity of another the UE. Toperform contention resolution, the UE may include a device identifier inthe Msg 3 1313 (e.g., a C-RNTI if assigned, a TC RNTI included in theMsg 2 1312, and/or any other suitable identifier).

The Msg 4 1314 may be received after or in response to the transmittingof the Msg 3 1313. If a C-RNTI was included in the Msg 3 1313, the basestation will address the UE on the PDCCH using the C-RNTI. If the UE’sunique C-RNTI is detected on the PDCCH, the random access procedure isdetermined to be successfully completed. If a TC-RNTI is included in theMsg 3 1313 (e.g., if the UE is in an RRC_IDLE state or not otherwiseconnected to the base station), Msg 4 1314 will be received using aDL-SCH associated with the TC-RNTI. If a MAC PDU is successfully decodedand a MAC PDU comprises the UE contention resolution identity MAC CEthat matches or otherwise corresponds with the CCCH SDU sent (e.g.,transmitted) in Msg 3 1313, the UE may determine that the contentionresolution is successful and/or the UE may determine that the randomaccess procedure is successfully completed.

The UE may be configured with a supplementary uplink (SUL) carrier and anormal uplink (NUL) carrier. An initial access (e.g., random accessprocedure) may be supported in an uplink carrier. For example, a basestation may configure the UE with two separate RACH configurations: onefor an SUL carrier and the other for an NUL carrier. For random accessin a cell configured with an SUL carrier, the network may indicate whichcarrier to use (NUL or SUL). The UE may determine the SUL carrier, forexample, if a measured quality of one or more reference signals is lowerthan a broadcast threshold. Uplink transmissions of the random accessprocedure (e.g., the Msg 1 1311 and/or the Msg 3 1313) may remain on theselected carrier. The UE may switch an uplink carrier during the randomaccess procedure (e.g., between the Msg 1 1311 and the Msg 3 1313) inone or more cases. For example, the UE may determine and/or switch anuplink carrier for the Msg 1 1311 and/or the Msg 3 1313 based on achannel clear assessment (e.g., a listen-before-talk).

FIG. 13B illustrates a two-step contention-free random access procedure.Similar to the four-step contention-based random access procedureillustrated in FIG. 13A, a base station may, prior to initiation of theprocedure, transmit a configuration message 1320 to the UE. Theconfiguration message 1320 may be analogous in some respects to theconfiguration message 1310. The procedure illustrated in FIG. 13Bcomprises transmission of two messages: a Msg 1 1321 and a Msg 2 1322.The Msg 1 1321 and the Msg 2 1322 may be analogous in some respects tothe Msg 1 1311 and a Msg 2 1312 illustrated in FIG. 13A, respectively.As will be understood from FIGS. 13A and 13B, the contention-free randomaccess procedure may not include messages analogous to the Msg 3 1313and/or the Msg 4 1314.

The contention-free random access procedure illustrated in FIG. 13B maybe initiated for a beam failure recovery, other SI request, SCelladdition, and/or handover. For example, a base station may indicate orassign to the UE the preamble to be used for the Msg 1 1321. The UE mayreceive, from the base station via PDCCH and/or RRC, an indication of apreamble (e.g., ra-PreambleIndex).

After transmitting a preamble, the UE may start a time window (e.g.,ra-ResponseWindow) to monitor a PDCCH for the RAR. In the event of abeam failure recovery request, the base station may configure the UEwith a separate time window and/or a separate PDCCH in a search spaceindicated by an RRC message (e.g., recoverySearchSpaceId). The UE maymonitor for a PDCCH transmission addressed to a Cell RNTI (C-RNTI) onthe search space. In the contention-free random access procedureillustrated in FIG. 13B, the UE may determine that a random accessprocedure successfully completes after or in response to transmission ofMsg 1 1321 and reception of a corresponding Msg 2 1322. The UE maydetermine that a random access procedure successfully completes, forexample, if a PDCCH transmission is addressed to a C-RNTI. The UE maydetermine that a random access procedure successfully completes, forexample, if the UE receives an RAR comprising a preamble identifiercorresponding to a preamble transmitted by the UE and/or the RARcomprises a MAC sub-PDU with the preamble identifier. The UE maydetermine the response as an indication of an acknowledgement for an SIrequest.

FIG. 13C illustrates another two-step random access procedure. Similarto the random access procedures illustrated in FIGS. 13A and 13B, a basestation may, prior to initiation of the procedure, transmit aconfiguration message 1330 to the UE. The configuration message 1330 maybe analogous in some respects to the configuration message 1310 and/orthe configuration message 1320. The procedure illustrated in FIG. 13Ccomprises transmission of two messages: a Msg A 1331 and a Msg B 1332.

Msg A 1331 may be transmitted in an uplink transmission by the UE. Msg A1331 may comprise one or more transmissions of a preamble 1341 and/orone or more transmissions of a transport block 1342. The transport block1342 may comprise contents that are similar and/or equivalent to thecontents of the Msg 3 1313 illustrated in FIG. 13A. The transport block1342 may comprise UCI (e.g., an SR, a HARQ ACK/NACK, and/or the like).The UE may receive the Msg B 1332 after or in response to transmittingthe Msg A 1331. The Msg B 1332 may comprise contents that are similarand/or equivalent to the contents of the Msg 2 1312 (e.g., an RAR)illustrated in FIGS. 13A and 13B and/or the Msg 4 1314 illustrated inFIG. 13A.

The UE may initiate the two-step random access procedure in FIG. 13C forlicensed spectrum and/or unlicensed spectrum. The UE may determine,based on one or more factors, whether to initiate the two-step randomaccess procedure. The one or more factors may be: a radio accesstechnology in use (e.g., LTE, NR, and/or the like); whether the UE hasvalid TA or not; a cell size; the UE’s RRC state; a type of spectrum(e.g., licensed vs. unlicensed); and/or any other suitable factors.

The UE may determine, based on two-step RACH parameters included in theconfiguration message 1330, a radio resource and/or an uplink transmitpower for the preamble 1341 and/or the transport block 1342 included inthe Msg A 1331. The RACH parameters may indicate a modulation and codingschemes (MCS), a time-frequency resource, and/or a power control for thepreamble 1341 and/or the transport block 1342. A time-frequency resourcefor transmission of the preamble 1341 (e.g., a PRACH) and atime-frequency resource for transmission of the transport block 1342(e.g., a PUSCH) may be multiplexed using FDM, TDM, and/or CDM. The RACHparameters may enable the UE to determine a reception timing and adownlink channel for monitoring for and/or receiving Msg B 1332.

The transport block 1342 may comprise data (e.g., delay-sensitive data),an identifier of the UE, security information, and/or device information(e.g., an International Mobile Subscriber Identity (IMSI)). The basestation may transmit the Msg B 1332 as a response to the Msg A 1331. TheMsg B 1332 may comprise at least one of following: a preambleidentifier; a timing advance command; a power control command; an uplinkgrant (e.g., a radio resource assignment and/or an MCS); a UE identifierfor contention resolution; and/or an RNTI (e.g., a C-RNTI or a TC-RNTI).The UE may determine that the two-step random access procedure issuccessfully completed if: a preamble identifier in the Msg B 1332 ismatched to a preamble transmitted by the UE; and/or the identifier ofthe UE in Msg B 1332 is matched to the identifier of the UE in the Msg A1331 (e.g., the transport block 1342).

A UE and a base station may exchange control signaling. The controlsignaling may be referred to as L1/L2 control signaling and mayoriginate from the PHY layer (e.g., layer 1) and/or the MAC layer (e.g.,layer 2). The control signaling may comprise downlink control signalingtransmitted from the base station to the UE and/or uplink controlsignaling transmitted from the UE to the base station.

The downlink control signaling may comprise: a downlink schedulingassignment; an uplink scheduling grant indicating uplink radio resourcesand/or a transport format; a slot format information; a preemptionindication; a power control command; and/or any other suitablesignaling. The UE may receive the downlink control signaling in apayload transmitted by the base station on a physical downlink controlchannel (PDCCH). The payload transmitted on the PDCCH may be referred toas downlink control information (DCI). In some scenarios, the PDCCH maybe a group common PDCCH (GC-PDCCH) that is common to a group of UEs.

A base station may attach one or more cyclic redundancy check (CRC)parity bits to a DCI in order to facilitate detection of transmissionerrors. When the DCI is intended for a UE (or a group of the UEs), thebase station may scramble the CRC parity bits with an identifier of theUE (or an identifier of the group of the UEs). Scrambling the CRC paritybits with the identifier may comprise Modulo-2 addition (or an exclusiveOR operation) of the identifier value and the CRC parity bits. Theidentifier may comprise a 16-bit value of a radio network temporaryidentifier (RNTI).

DCIs may be used for different purposes. A purpose may be indicated bythe type of RNTI used to scramble the CRC parity bits. For example, aDCI having CRC parity bits scrambled with a paging RNTI (P-RNTI) mayindicate paging information and/or a system information changenotification. The P-RNTI may be predefined as “FFFE” in hexadecimal. ADCI having CRC parity bits scrambled with a system information RNTI(SI-RNTI) may indicate a broadcast transmission of the systeminformation. The SI-RNTI may be predefined as “FFFF” in hexadecimal. ADCI having CRC parity bits scrambled with a random access RNTI (RA-RNTI)may indicate a random access response (RAR). A DCI having CRC paritybits scrambled with a cell RNTI (C-RNTI) may indicate a dynamicallyscheduled unicast transmission and/or a triggering of PDCCH-orderedrandom access. A DCI having CRC parity bits scrambled with a temporarycell RNTI (TC-RNTI) may indicate a contention resolution (e.g., a Msg 3analogous to the Msg 3 1313 illustrated in FIG. 13A). Other RNTIsconfigured to the UE by a base station may comprise a ConfiguredScheduling RNTI (CS-RNTI), a Transmit Power Control-PUCCH RNTI(TPC-PUCCH-RNTI), a Transmit Power Control-PUSCH RNTI (TPC-PUSCH-RNTI),a Transmit Power Control-SRS RNTI (TPC-SRS-RNTI), an Interruption RNTI(INT-RNTI), a Slot Format Indication RNTI (SFI-RNTI), a Semi-PersistentCSI RNTI (SP-CSI-RNTI), a Modulation and Coding Scheme Cell RNTI(MCS-C-RNTI), and/or the like.

Depending on the purpose and/or content of a DCI, the base station maytransmit the DCIs with one or more DCI formats. For example, DCI format0_0 may be used for scheduling of PUSCH in a cell. DCI format 0_0 may bea fallback DCI format (e.g., with compact DCI payloads). DCI format 0_1may be used for scheduling of PUSCH in a cell (e.g., with more DCIpayloads than DCI format 0_0). DCI format 1_0 may be used for schedulingof PDSCH in a cell. DCI format 1_0 may be a fallback DCI format (e.g.,with compact DCI payloads). DCI format 1_1 may be used for scheduling ofPDSCH in a cell (e.g., with more DCI payloads than DCI format 1_0). DCIformat 2_0 may be used for providing a slot format indication to a groupof UEs. DCI format 2_1 may be used for notifying a group of UEs of aphysical resource block and/or OFDM symbol where the UE may assume notransmission is intended to the UE. DCI format 2_2 may be used fortransmission of a transmit power control (TPC) command for PUCCH orPUSCH. DCI format 2_3 may be used for transmission of a group of TPCcommands for SRS transmissions by one or more UEs. DCI format(s) for newfunctions may be defined in future releases. DCI formats may havedifferent DCI sizes, or may share the same DCI size.

After scrambling a DCI with a RNTI, the base station may process the DCIwith channel coding (e.g., polar coding), rate matching, scramblingand/or QPSK modulation. A base station may map the coded and modulatedDCI on resource elements used and/or configured for a PDCCH. Based on apayload size of the DCI and/or a coverage of the base station, the basestation may transmit the DCI via a PDCCH occupying a number ofcontiguous control channel elements (CCEs). The number of the contiguousCCEs (referred to as aggregation level) may be 1, 2, 4, 8, 16, and/orany other suitable number. A CCE may comprise a number (e.g., 6) ofresource-element groups (REGs). A REG may comprise a resource block inan OFDM symbol. The mapping of the coded and modulated DCI on theresource elements may be based on mapping of CCEs and REGs (e.g.,CCE-to-REG mapping).

FIG. 14A illustrates an example of CORESET configurations for abandwidth part. The base station may transmit a DCI via a PDCCH on oneor more control resource sets (CORESETs). A CORESET may comprise atime-frequency resource in which the UE tries to decode a DCI using oneor more search spaces. The base station may configure a CORESET in thetime-frequency domain. In the example of FIG. 14A, a first CORESET 1401and a second CORESET 1402 occur at the first symbol in a slot. The firstCORESET 1401 overlaps with the second CORESET 1402 in the frequencydomain. A third CORESET 1403 occurs at a third symbol in the slot. Afourth CORESET 1404 occurs at the seventh symbol in the slot. CORESETsmay have a different number of resource blocks in frequency domain.

FIG. 14B illustrates an example of a CCE-to-REG mapping for DCItransmission on a CORESET and PDCCH processing. The CCE-to-REG mappingmay be an interleaved mapping (e.g., for the purpose of providingfrequency diversity) or a non-interleaved mapping (e.g., for thepurposes of facilitating interference coordination and/orfrequency-selective transmission of control channels). The base stationmay perform different or same CCE-to-REG mapping on different CORESETs.A CORESET may be associated with a CCE-to-REG mapping by RRCconfiguration. A CORESET may be configured with an antenna port quasico-location (QCL) parameter. The antenna port QCL parameter may indicateQCL information of a demodulation reference signal (DMRS) for PDCCHreception in the CORESET.

The base station may transmit, to the UE, RRC messages comprisingconfiguration parameters of one or more CORESETs and one or more searchspace sets. The configuration parameters may indicate an associationbetween a search space set and a CORESET. A search space set maycomprise a set of PDCCH candidates formed by CCEs at a given aggregationlevel. The configuration parameters may indicate: a number of PDCCHcandidates to be monitored per aggregation level; a PDCCH monitoringperiodicity and a PDCCH monitoring pattern; one or more DCI formats tobe monitored by the UE; and/or whether a search space set is a commonsearch space set or a UE-specific search space set. A set of CCEs in thecommon search space set may be predefined and known to the UE. A set ofCCEs in the UE-specific search space set may be configured based on theUE’s identity (e.g., C-RNTI).

As shown in FIG. 14B, the UE may determine a time-frequency resource fora CORESET based on RRC messages. The UE may determine a CCE-to-REGmapping (e.g., interleaved or non-interleaved, and/or mappingparameters) for the CORESET based on configuration parameters of theCORESET. The UE may determine a number (e.g., at most 10) of searchspace sets configured on the CORESET based on the RRC messages. The UEmay monitor a set of PDCCH candidates according to configurationparameters of a search space set. The UE may monitor a set of PDCCHcandidates in one or more CORESETs for detecting one or more DCIs.Monitoring may comprise decoding one or more PDCCH candidates of the setof the PDCCH candidates according to the monitored DCI formats.Monitoring may comprise decoding a DCI content of one or more PDCCHcandidates with possible (or configured) PDCCH locations, possible (orconfigured) PDCCH formats (e.g., number of CCEs, number of PDCCHcandidates in common search spaces, and/or number of PDCCH candidates inthe UE-specific search spaces) and possible (or configured) DCI formats.The decoding may be referred to as blind decoding. The UE may determinea DCI as valid for the UE, in response to CRC checking (e.g., scrambledbits for CRC parity bits of the DCI matching a RNTI value). The UE mayprocess information contained in the DCI (e.g., a scheduling assignment,an uplink grant, power control, a slot format indication, a downlinkpreemption, and/or the like).

The UE may transmit uplink control signaling (e.g., uplink controlinformation (UCI)) to a base station. The uplink control signaling maycomprise hybrid automatic repeat request (HARQ) acknowledgements forreceived DL-SCH transport blocks. The UE may transmit the HARQacknowledgements after receiving a DL-SCH transport block. Uplinkcontrol signaling may comprise channel state information (CSI)indicating channel quality of a physical downlink channel. The UE maytransmit the CSI to the base station. The base station, based on thereceived CSI, may determine transmission format parameters (e.g.,comprising multi-antenna and beamforming schemes) for a downlinktransmission. Uplink control signaling may comprise scheduling requests(SR). The UE may transmit an SR indicating that uplink data is availablefor transmission to the base station. The UE may transmit a UCI (e.g.,HARQ acknowledgements (HARQ-ACK), CSI report, SR, and the like) via aphysical uplink control channel (PUCCH) or a physical uplink sharedchannel (PUSCH). The UE may transmit the uplink control signaling via aPUCCH using one of several PUCCH formats.

There may be five PUCCH formats and the UE may determine a PUCCH formatbased on a size of the UCI (e.g., a number of uplink symbols of UCItransmission and a number of UCI bits). PUCCH format 0 may have a lengthof one or two OFDM symbols and may include two or fewer bits. The UE maytransmit UCI in a PUCCH resource using PUCCH format 0 if thetransmission is over one or two symbols and the number of HARQ-ACKinformation bits with positive or negative SR (HARQ-ACK/SR bits) is oneor two. PUCCH format 1 may occupy a number between four and fourteenOFDM symbols and may include two or fewer bits. The UE may use PUCCHformat 1 if the transmission is four or more symbols and the number ofHARQ-ACK/SR bits is one or two. PUCCH format 2 may occupy one or twoOFDM symbols and may include more than two bits. The UE may use PUCCHformat 2 if the transmission is over one or two symbols and the numberof UCI bits is two or more. PUCCH format 3 may occupy a number betweenfour and fourteen OFDM symbols and may include more than two bits. TheUE may use PUCCH format 3 if the transmission is four or more symbols,the number of UCI bits is two or more and PUCCH resource does notinclude an orthogonal cover code. PUCCH format 4 may occupy a numberbetween four and fourteen OFDM symbols and may include more than twobits. The UE may use PUCCH format 4 if the transmission is four or moresymbols, the number of UCI bits is two or more and the PUCCH resourceincludes an orthogonal cover code.

The base station may transmit configuration parameters to the UE for aplurality of PUCCH resource sets using, for example, an RRC message. Theplurality of PUCCH resource sets (e.g., up to four sets) may beconfigured on an uplink BWP of a cell. A PUCCH resource set may beconfigured with a PUCCH resource set index, a plurality of PUCCHresources with a PUCCH resource being identified by a PUCCH resourceidentifier (e.g., pucch-Resourceid), and/or a number (e.g. a maximumnumber) of UCI information bits the UE may transmit using one of theplurality of PUCCH resources in the PUCCH resource set. When configuredwith a plurality of PUCCH resource sets, the UE may select one of theplurality of PUCCH resource sets based on a total bit length of the UCIinformation bits (e.g., HARQ-ACK, SR, and/or CSI). If the total bitlength of UCI information bits is two or fewer, the UE may select afirst PUCCH resource set having a PUCCH resource set index equal to “0”.If the total bit length of UCI information bits is greater than two andless than or equal to a first configured value, the UE may select asecond PUCCH resource set having a PUCCH resource set index equal to“1”. If the total bit length of UCI information bits is greater than thefirst configured value and less than or equal to a second configuredvalue, the UE may select a third PUCCH resource set having a PUCCHresource set index equal to “2”. If the total bit length of UCIinformation bits is greater than the second configured value and lessthan or equal to a third value (e.g., 1406), the UE may select a fourthPUCCH resource set having a PUCCH resource set index equal to “3”.

After determining a PUCCH resource set from a plurality of PUCCHresource sets, the UE may determine a PUCCH resource from the PUCCHresource set for UCI (HARQ-ACK, CSI, and/or SR) transmission. The UE maydetermine the PUCCH resource based on a PUCCH resource indicator in aDCI (e.g., with a DCI format 1_0 or DCI for 1_1) received on a PDCCH. Athree-bit PUCCH resource indicator in the DCI may indicate one of eightPUCCH resources in the PUCCH resource set. Based on the PUCCH resourceindicator, the UE may transmit the UCI (HARQ-ACK, CSI and/or SR) using aPUCCH resource indicated by the PUCCH resource indicator in the DCI.

FIG. 15 illustrates an example of a wireless device 1502 incommunication with a base station 1504 in accordance with embodiments ofthe present disclosure. The wireless device 1502 and base station 1504may be part of a mobile communication network, such as the mobilecommunication network 100 illustrated in FIG. 1A, the mobilecommunication network 150 illustrated in FIG. 1B, or any othercommunication network. Only one wireless device 1502 and one basestation 1504 are illustrated in FIG. 15 , but it will be understood thata mobile communication network may include more than one UE and/or morethan one base station, with the same or similar configuration as thoseshown in FIG. 15 .

The base station 1504 may connect the wireless device 1502 to a corenetwork (not shown) through radio communications over the air interface(or radio interface) 1506. The communication direction from the basestation 1504 to the wireless device 1502 over the air interface 1506 isknown as the downlink, and the communication direction from the wirelessdevice 1502 to the base station 1504 over the air interface is known asthe uplink. Downlink transmissions may be separated from uplinktransmissions using FDD, TDD, and/or some combination of the twoduplexing techniques.

In the downlink, data to be sent to the wireless device 1502 from thebase station 1504 may be provided to the processing system 1508 of thebase station 1504. The data may be provided to the processing system1508 by, for example, a core network. In the uplink, data to be sent tothe base station 1504 from the wireless device 1502 may be provided tothe processing system 1518 of the wireless device 1502. The processingsystem 1508 and the processing system 1518 may implement layer 3 andlayer 2 OSI functionality to process the data for transmission. Layer 2may include an SDAP layer, a PDCP layer, an RLC layer, and a MAC layer,for example, with respect to FIG. 2A, FIG. 2B, FIG. 3 , and FIG. 4A.Layer 3 may include an RRC layer as with respect to FIG. 2B.

After being processed by processing system 1508, the data to be sent tothe wireless device 1502 may be provided to a transmission processingsystem 1510 of base station 1504. Similarly, after being processed bythe processing system 1518, the data to be sent to base station 1504 maybe provided to a transmission processing system 1520 of the wirelessdevice 1502. The transmission processing system 1510 and thetransmission processing system 1520 may implement layer 1 OSIfunctionality. Layer 1 may include a PHY layer with respect to FIG. 2A,FIG. 2B, FIG. 3 , and FIG. 4A. For transmit processing, the PHY layermay perform, for example, forward error correction coding of transportchannels, interleaving, rate matching, mapping of transport channels tophysical channels, modulation of physical channel, multiple-inputmultiple-output (MIMO) or multi-antenna processing, and/or the like.

At the base station 1504, a reception processing system 1512 may receivethe uplink transmission from the wireless device 1502. At the wirelessdevice 1502, a reception processing system 1522 may receive the downlinktransmission from base station 1504. The reception processing system1512 and the reception processing system 1522 may implement layer 1 OSIfunctionality. Layer 1 may include a PHY layer with respect to FIG. 2A,FIG. 2B, FIG. 3 , and FIG. 4A. For receive processing, the PHY layer mayperform, for example, error detection, forward error correctiondecoding, deinterleaving, demapping of transport channels to physicalchannels, demodulation of physical channels, MIMO or multi-antennaprocessing, and/or the like.

As shown in FIG. 15 , a wireless device 1502 and the base station 1504may include multiple antennas. The multiple antennas may be used toperform one or more MIMO or multi-antenna techniques, such as spatialmultiplexing (e.g., single-user MIMO or multi-user MIMO),transmit/receive diversity, and/or beamforming. In other examples, thewireless device 1502 and/or the base station 1504 may have a singleantenna.

The processing system 1508 and the processing system 1518 may beassociated with a memory 1514 and a memory 1524, respectively. Memory1514 and memory 1524 (e.g., one or more non-transitory computer readablemediums) may store computer program instructions or code that may beexecuted by the processing system 1508 and/or the processing system 1518to carry out one or more of the functionalities discussed in the presentapplication. Although not shown in FIG. 15 , the transmission processingsystem 1510, the transmission processing system 1520, the receptionprocessing system 1512, and/or the reception processing system 1522 maybe coupled to a memory (e.g., one or more non-transitory computerreadable mediums) storing computer program instructions or code that maybe executed to carry out one or more of their respectivefunctionalities.

The processing system 1508 and/or the processing system 1518 maycomprise one or more controllers and/or one or more processors. The oneor more controllers and/or one or more processors may comprise, forexample, a general-purpose processor, a digital signal processor (DSP),a microcontroller, an application specific integrated circuit (ASIC), afield programmable gate array (FPGA) and/or other programmable logicdevice, discrete gate and/or transistor logic, discrete hardwarecomponents, an on-board unit, or any combination thereof. The processingsystem 1508 and/or the processing system 1518 may perform at least oneof signal coding/processing, data processing, power control,input/output processing, and/or any other functionality that may enablethe wireless device 1502 and the base station 1504 to operate in awireless environment.

The processing system 1508 and/or the processing system 1518 may beconnected to one or more peripherals 1516 and one or more peripherals1526, respectively. The one or more peripherals 1516 and the one or moreperipherals 1526 may include software and/or hardware that providefeatures and/or functionalities, for example, a speaker, a microphone, akeypad, a display, a touchpad, a power source, a satellite transceiver,a universal serial bus (USB) port, a hands-free headset, a frequencymodulated (FM) radio unit, a media player, an Internet browser, anelectronic control unit (e.g., for a motor vehicle), and/or one or moresensors (e.g., an accelerometer, a gyroscope, a temperature sensor, aradar sensor, a lidar sensor, an ultrasonic sensor, a light sensor, acamera, and/or the like). The processing system 1508 and/or theprocessing system 1518 may receive user input data from and/or provideuser output data to the one or more peripherals 1516 and/or the one ormore peripherals 1526. The processing system 1518 in the wireless device1502 may receive power from a power source and/or may be configured todistribute the power to the other components in the wireless device1502. The power source may comprise one or more sources of power, forexample, a battery, a solar cell, a fuel cell, or any combinationthereof. The processing system 1508 and/or the processing system 1518may be connected to a GPS chipset 1517 and a GPS chipset 1527,respectively. The GPS chipset 1517 and the GPS chipset 1527 may beconfigured to provide geographic location information of the wirelessdevice 1502 and the base station 1504, respectively.

FIG. 16A illustrates an example structure for uplink transmission. Abaseband signal representing a physical uplink shared channel mayperform one or more functions. The one or more functions may comprise atleast one of: scrambling; modulation of scrambled bits to generatecomplex-valued symbols; mapping of the complex-valued modulation symbolsonto one or several transmission layers; transform precoding to generatecomplex-valued symbols; precoding of the complex-valued symbols; mappingof precoded complex-valued symbols to resource elements; generation ofcomplex-valued time-domain Single Carrier-Frequency Division MultipleAccess (SC-FDMA) or CP-OFDM signal for an antenna port; and/or the like.In an example, when transform precoding is enabled, a SC-FDMA signal foruplink transmission may be generated. In an example, when transformprecoding is not enabled, an CP-OFDM signal for uplink transmission maybe generated by FIG. 16A. These functions are illustrated as examplesand it is anticipated that other mechanisms may be implemented invarious embodiments.

FIG. 16B illustrates an example structure for modulation andup-conversion of a baseband signal to a carrier frequency. The basebandsignal may be a complex-valued SC-FDMA or CP-OFDM baseband signal for anantenna port and/or a complex-valued Physical Random Access Channel(PRACH) baseband signal. Filtering may be employed prior totransmission.

FIG. 16C illustrates an example structure for downlink transmissions. Abaseband signal representing a physical downlink channel may perform oneor more functions. The one or more functions may comprise: scrambling ofcoded bits in a codeword to be transmitted on a physical channel;modulation of scrambled bits to generate complex-valued modulationsymbols; mapping of the complex-valued modulation symbols onto one orseveral transmission layers; precoding of the complex-valued modulationsymbols on a layer for transmission on the antenna ports; mapping ofcomplex-valued modulation symbols for an antenna port to resourceelements; generation of complex-valued time-domain OFDM signal for anantenna port; and/or the like. These functions are illustrated asexamples and it is anticipated that other mechanisms may be implementedin various embodiments.

FIG. 16D illustrates another example structure for modulation andup-conversion of a baseband signal to a carrier frequency. The basebandsignal may be a complex-valued OFDM baseband signal for an antenna port.Filtering may be employed prior to transmission.

A wireless device may receive from a base station one or more messages(e.g. RRC messages) comprising configuration parameters of a pluralityof cells (e.g. primary cell, secondary cell). The wireless device maycommunicate with at least one base station (e.g. two or more basestations in dual-connectivity) via the plurality of cells. The one ormore messages (e.g. as a part of the configuration parameters) maycomprise parameters of physical, MAC, RLC, PCDP, SDAP, RRC layers forconfiguring the wireless device. For example, the configurationparameters may comprise parameters for configuring physical and MAClayer channels, bearers, etc. For example, the configuration parametersmay comprise parameters indicating values of timers for physical, MAC,RLC, PCDP, SDAP, RRC layers, and/or communication channels.

A timer may begin running once it is started and continue running untilit is stopped or until it expires. A timer may be started if it is notrunning or restarted if it is running. A timer may be associated with avalue (e.g. the timer may be started or restarted from a value or may bestarted from zero and expire once it reaches the value). The duration ofa timer may not be updated until the timer is stopped or expires (e.g.,due to BWP switching). A timer may be used to measure a timeperiod/window for a process. When the specification refers to animplementation and procedure related to one or more timers, it will beunderstood that there are multiple ways to implement the one or moretimers. For example, it will be understood that one or more of themultiple ways to implement a timer may be used to measure a timeperiod/window for the procedure. For example, a random access responsewindow timer may be used for measuring a window of time for receiving arandom access response. In an example, instead of starting and expiry ofa random access response window timer, the time difference between twotime stamps may be used. When a timer is restarted, a process formeasurement of time window may be restarted. Other exampleimplementations may be provided to restart a measurement of a timewindow.

A wireless device may make (e.g., set up, (re-)establish, and/or resume)a connection (e.g., RRC connection) to a network for transmission(s) ofdata. For example, to transmit the data (e.g., the data from DTCH), anRRC state of the wireless device may be an RRC_CONNECTED state. Forexample, the wireless device may not perform (e.g., may not be allowedto perform or may prohibit) an uplink transmission in aNon-RRC_CONNECTED (e.g., an RRC_INACTIVE state and/or an RRC_IDLEstate). The data may be DL (e.g., mobile terminated (MT)) data and/or UL(e.g., mobile originated (MO)) data.

For example, a wireless device may perform one or more procedures tomake the connection to the network in the RRC_INACTIVE state (or theRRC-IDLE state). For example, the one or more procedures comprise aconnection setup procedure, connection a (re-)establish procedure,and/or a connection resume procedure. For example, the wireless devicemay perform the one or more procedures, e.g., when DL (e.g., mobileterminated (MT)) and/or UL (e.g., mobile originated (MO)) data areavailable in a buffer. Based on the one or more procedures (e.g., inresponse to successfully completing the connection setup or resumeprocedure), the RRC state of the wireless device may transition to anRRC_CONNECTED state from a Non-RRC_CONNECTED state (e.g., anRRC_INACTIVE state and/or an RRC_IDLE state). The wireless device mayreceive DL data and/or DL signal(s) via DL transmission(s) and/or maytransmit UL data and/or UL signal(s) via UL transmission in theRRC_CONNECTED state. The wireless device may transition to theNon-RRC_CONNECTED from RRC_CONNECTED state, e.g., after or in responseto no more DL data (e.g., to be received) and/or no more UL data (e.g.,to be transmitted) in buffer(s). To transition to the Non-RRC_CONNECTEDstate from the RRC_CONNECTED state, the wireless device may perform aconnection release procedure. The connection release procedure (e.g., anRRC release procedure) may result in transitioning the RRC state to theNon-RRC_CONNECTED state.

A frequent RRC state transition between RRC states (e.g., between aNon-RRC_CONNECTED state and an RRC_CONNECTED state) may require awireless device to transmit and/or receive a plurality of controlsignals (e.g., RRC message(s), MAC CE(s), and/or DCI(s)) in one or morelayers (e.g., RRC layer, MAC layer, and/or PHY layer).

For example, for an RRC connection setup, a wireless device maytransmit, to a base station, an RRC connection setup request and receivean RRC connection setup message as a respond to the RRC connection setuprequest. For example, for an RRC connection resume, the wireless devicemay transmit, to a base station, an RRC connection resume request andreceive an RRC connection resume message as a respond to the RRCconnection resume request. For example, for an RRC connection release,the wireless device may receive, from a base station, an RRC connectionrelease request.

For example, for DL and/or UL transmission of small data available (orarrival) in the Non-RRC_CONNECTED, it may be inefficient for a wirelessdevice to make (or resume) an connection to a network (e.g., transitionto an RRC_CONNECTED state from a Non-RRC_CONNECTED state) and releasethe connection (e.g., transition to a Non-RRC_CONNECTED state from anRRC_CONNECTED state) after or in response to perform the DL and/or ULtransmission of small data in an RRC_CONNECTED state. This may result inincreasing unnecessary power consumption and/or signaling overhead. Forexample, the signaling overhead (e.g., control signaling overhead for anRRC connection and/or an RRC release) required to transmit a payload maybe larger than the payload. For example, a frequent RRC state transitionfor the small and infrequent DL and/or UL data packet(s) may causeunnecessary power consumption and signaling overhead for the wirelessdevice.

Examples of small and infrequent data packets may be such trafficgenerated from smartphone applications, Instant Messaging (IM) services,heart-beat/keep-alive traffic from IM/email clients and other apps, pushnotifications from various applications, non-smartphone applications,wearables (e.g., positioning information), sensors (e.g., fortransmitting temperature, pressure readings periodically or in an eventtriggered manner), and/or smart meters and smart meter networks sendingmeter readings.

Transmission(s) (e.g., DL and/or UL transmission(s)) in aNon-RRC_CONNECTED state may be beneficial. For example, a wirelessdevice may transmit and/or receive one or more data packets in aNon-RRC_CONNECTED state. For example, a wireless device may transmitand/or receive one or more data packets without making a connectionwhile keeping an RRC state as a Non-RRC_ CONNECTED state.

For example, a wireless device may receive, from a base station,scheduling information (e.g., RRC message and/or SIB) indicating one ormore uplink radio resources in the Non-RRC_CONNECTED state for thewireless device. The one or more uplink radio resources may be forinfrequent data transmission. The one or more uplink radio resources maybe for non-periodic data transmission. The one or more uplink radioresources may be for periodic data transmission. The wireless device maytransmit the one or more data packets via the one or more radioresources while keeping its RRC state as the Non-RRC_CONNECTED state.For example, the wireless device may not transition its RRC state to theRRC_CONNECTED to transmit the one or more data packets. The uplinktransmission(s) via the one or more radio resources in aNon-RRC_CONNECTED state may be efficient and flexible (e.g., for lowthroughput short data bursts). The uplink transmission(s) via the one ormore radio resources in a Non-RRC_CONNECTED state may provide efficientsignaling mechanisms (e.g., signaling overhead is less than payload).The uplink transmission(s) via the one or more radio resources in aNon-RRC_CONNECTED state may reduce signaling overhead. The uplinktransmission(s) via the one or more radio resources in aNon-RRC_CONNECTED state may improve the battery performance of thewireless device. For example, a wireless device that has intermittentsmall data packets in the Non-RRC_CONNECTED state may benefit from suchuplink transmission(s) in the Non-RRC_CONNECTED state.

Uplink transmission(s) in a Non-RRC_CONNECTED state may be based on arandom access (RA) procedure. For example, the wireless device maytransmit at least one preamble of the RA procedure to perform the uplinktransmission(s). For example, a wireless device may transmit uplink data(e.g., SDU of DTCH) via Msg A PUSCH and/or Msg 3 PUSCH during the RAprocedure. The wireless device may keep (or maintain) an RRC state asthe Non-RRC_CONNECTED state during and/or after the RA procedure. Forexample, after or in response to completing the transmission of theuplink data and/or completing the RA procedure, the wireless device maykeep (or maintain) an RRC state as the Non-RRC_CONNECTED state.

Uplink transmission in a Non-RRC_CONNECTED state may be based onpre-configured PUSCH resource(s). For example, a wireless device mayreceive resource configuration parameters indicating UL grant(s) and/orthe pre-configured PUSCH resource(s) of the UL grant(s). The wirelessdevice may transmit uplink data (e.g., associated with DTCH) using theUL grant(s) and/or via the pre-configured PUSCH resource(s) of the ULgrant(s) in the Non-RRC_CONNECTED state.

Uplink data transmission(s) in a Non-RRC_CONNECTED state may be referredto as small data transmission (SDT), early data transmission (EDT),and/or data transmission via (pre-)configured uplink resource(s) (PURs).For example, in the present disclosure, an SDT and/or an EDT may beinterchangeable with uplink data transmission(s) in a Non-RRC_CONNECTEDstate. For example, in the present disclosure, radio resource(s) usedfor an SDT in a Non-RRC_CONNECTED state may be referred to as PUR(s).For example, uplink transmission(s) based on a RA procedure in aNon-RRC_CONNECTED state may be referred to as an RA-based SDT, anRA-based EDT, an EDT, and/or the like. For example, an uplinktransmission based on (pre-)configured grant(s) in a Non-RRC_CONNECTEDstate may be referred to as (pre-)configured grant based SDT (CG-basedSDT). One or more radio resources of the (pre)configured grant(s) may bereferred to as (pre)configured uplink resources (PURs), SDT resources,resources of SDT, and/or the like.

FIG. 17 illustrates uplink data transmission in a Non-RRC_CONNECTEDstate as per an aspect of an example embodiment of the presentdisclosure. The wireless device may receive one or more messagescomprising configuration parameters for the uplink data transmission.The wireless device may receive the one or more messages in theRRC_CONNECTED state. The wireless device may receive the one or moremessages in the Non-RRC_CONNECTED state. The one or more messages may bebroadcast, e.g., system information block. The one or more messages maybe wireless-device-specific, e.g., an RRC message, MAC CE, and/or a DCIdedicated to the wireless device. For example, the one or more messagescomprise an RRC release message. The configuration parameters mayindicate uplink grant(s) and/or radio resource(s) available, scheduled,and/or configured for SDT(s) during the Non-RRC_CONNECTED state. Thewireless device may keep the RRC state as the Non-RRC_CONNECTED state,e.g., after or while performing the SDT(s).

In FIG. 17 , a wireless device may determine to transition an RRC stateof the wireless device to a Non-RRC_CONNECTED state from anRRC_CONNECTED state. The wireless device may determine to transition anRRC state to the Non-RRC_CONNECTED state after or in response toreceiving an RRC message.

For example, a wireless device may receive, from a base station, an RRCmessage (e.g., RRC release message). The RRC message (e.g., RRC releasemessage) may indicate a release of an RRC connection from a network. Inresponse to receiving the RRC message, the wireless device may performan RRC release procedure. The RRC release procedure may comprise arelease and/or a suspension of an established radio bearers and/orconfigured radio resources. The RRC release procedure may comprise asuspension of the RRC connection (e.g., if a signaling radio bearer(SRB) (e.g., SRB2) and/or at least one dedicated radio bearer (DRB) aresetup) and/or a suspension of the established radio bearer(s). Afterand/or in response to receiving the RRC message (or performing the RRCrelease procedure), the wireless device may determine to transition anRRC state of the wireless devices to a Non-RRC_CONNECTED state from anRRC_CONNECTED state.

In FIG. 17 . a wireless device may determine to transition an RRC stateof the wireless device from a Non-RRC_CONNECTED state to anRRC_CONNECTED state. For example, the wireless device may perform arandom access procedure to transition to the RRC_CONNECTED state. Thewireless device may transition to the RRC_CONNECTED state without arandom access procedure.

For example, a wireless device may transition to the RRC_CONNECTED statevia a random access procedure. For example, a wireless device mayperform (and/or initiate) the random access procedure for an SDT. Forexample, the wireless device may perform the random access procedure asan RA-based SDT. The wireless device may perform (and/or initiate) therandom access procedure for an initial access. For example, the initialaccess may be initiated based on receiving, by the wireless device, apaging message. For example, the initial access may be initiated basedon a cell (re)selection procedure performed by the wireless. Thewireless device may receive a message (e.g., Msg B, Msg 4, RRC setup,and/or RRC resume messages) comprising an indication of transitioning tothe RRC_CONNECTED state. The wireless device may transition to theRRC_CONNECTED state, e.g., after or in response to receiving themessage.

For example, a wireless device may perform (and/or initiate) a CG-basedSDT for uplink transmission of uplink data in the Non-RRC_CONNECTEDstate. The wireless device may monitor, based on the CG-based SDT, aPDCCH in the Non-RRC CONNECTED state. For example, the CG-based SDT mayrequire the wireless device to monitor the PDCCH, e.g., to receive aresponse to the uplink transmission and/or to receive uplink grant(s)and/or downlink assignment(s). For example, the wireless device maymonitor the PDCCH in response to transmitting the uplink data via theCG-based SDT. The wireless device may monitor the PDCCH during a periodof time (e.g., during a time window and/or a time interval) that ispredefined and/or configured by a base station to the wireless device.The wireless device may receive, via the PDCCH during the period oftime, downlink control message(s) (e.g., DCI) comprising a downlinkassignment (e.g., that schedules a downlink transmission). The wirelessdevice may receive based on the downlink assignment, a message (e.g.,RRC setup and/or RRC resume) comprising an indication of transitioningto the RRC_CONNECTED state. The wireless device may transition to theRRC_CONNECTED state, e.g., after or in response to receiving themessage. In this case, the wireless device may make an RRC connection toa network (or a base station) via the CG-based SDT. For example, thewireless device may make an RRC connection to a network (or a basestation) without a random access procedure.

A wireless device may receive, from a base station, one or moreconfiguration parameters that indicates and/or comprise a number ofoccasions of the one or more uplink radio resources (e.g., an exampleparameter name: NumOccasions). The number of occasions may indicate thatthe one or more uplink radio resources is one time use resource (orgrant) for a single uplink transmission. The number of occasions mayindicate that the one or more uplink radio resources is a plurality ofuplink radio resources. The number of occasions may indicate that theone or more uplink radio resources is one or more periodic radioresources.

For example, the one or more uplink radio resources may be for CG-basedSDT and/or RA-based SDT. For example, the wireless device may receiveone or more RRC messages (e.g., a broadcast, multicast, and/or wirelessspecific messages) comprising the one or more configuration parameters.The wireless device may receive at least one of the one or more RRCmessages in an RRC_CONNECTED state. The wireless device may receive atleast one of the one or more RRC messages in a Non-RRC_CONNECTED state.

A wireless device may initiate a random access (RA) procedure (e.g.,RA-based SDT and/or EDT) on a cell to transmit, via the cell, uplinkdata in a Non-RRC_CONNECTED state. For example, the uplink data may beassociated with a particular logical channel. For example, the uplinkdata may comprise a service data unit (SDU) from a particular logicalchannel (e.g., DTCH). The wireless device may keep its RRC state as theNon-RRC_CONNECTED state while performing the RA procedure and/or whiletransmitting the uplink data during the RA procedure. The wirelessdevice may keep the Non-RRC_CONNECTED state in response to or aftercompleting the RA procedure and/or completing the transmission of theuplink data.

A network or a base station may indicate which cell is available fortransmission (e.g., SDT and/or EDT) of uplink data (e.g., associatedwith DTCH) in a Non-RRC_CONNECTED state. The wireless device mayreceive, from the base station via a cell, a message (e.g., broadcast,multicast, and/or unicast message) indicating whether the transmissionof the uplink data on the cell is available in the Non-RRC_CONNECTEDstate. For example, a message (e.g., broadcast, multicast, and/orunicast message) may indicate whether an RA-based SDT (e.g., EDT) on thecell is available in the Non-RRC_CONNECTED state. For example, a message(e.g., broadcast, multicast, and/or unicast message) may indicatewhether a CG-based SDT (e.g., PUR) on the cell is available in theNon-RRC_CONNECTED state. For example, a message (e.g., broadcast,multicast, and/or unicast message) may indicate whether an SDT (e.g.,RA-based SDT and/or CG-based SDT) on the cell is available in theNon-RRC_CONNECTED state. For example, the message may be a broadcast(multicast) system information block(s) of a cell and/or an RRC messagededicated to the wireless device.

In an example, an RRC message (e.g., system information block(s)) that awireless device receive via a cell may comprise one or more parametersindicating whether to allow the wireless device to perform, via thecell, the transmission of uplink data in a Non-RRC_CONNECTED state. Theone or more parameters may be a field indicating that the wirelessdevice is allowed to initiate an RA-based SDT on the cell. Theindication may be true (e.g., initiating the RA-based SDT is allowed) orfalse (e.g., initiating the RA-based SDT is not allowed). The indicationmay be a presence of the field (e.g., initiating the RA-based SDT isallowed) or an absence of the field (e.g., initiating the RA-based SDTis not allowed).

The field may indicate that the wireless device is allowed to initiateRA-based SDT on the cell for transmission of a particular type of data.For example, the particular type of data may comprise control plane (CP)data, user plane (UP) data, mobile originating (MO) data (or call),and/or mobile terminating (MT) data (or call), and/or the like. Exampleformats of the field for CP and UP data may be:

cp-SDT ENUMERATED {true}   OPTIONAL, -- Need ORup-SDT ENUMERATED {true}   OPTIONAL, -- Need OR.

cp-SDT (=true) and up-SDT (=true) may respectively indicate the wirelessdevice is allowed to initiate SDT for transmission of CP data and UPdata.

The field may indicate that the wireless device is allowed to initiateRA-based SDT on the cell when connected to a particular type of network.For example, the particular type of network may comprise an evolvedpacket core (EPC) network, a 5G core (5GC) network, and/or the like. Thefield may indicate that the wireless device is allowed to initiate anRA-based SDT on the cell for transmission of a particular type of datawhen connected to the particular type of network. Example formats of thefield for transmission of CP data via EPC or 5GC may be:

cp-SDT-EPC   ENUMERATED {true}   OPTIONAL, -- Need ORcp-SDT-5GC   ENUMERATED {true}   OPTIONAL, -- Need OR.

cp-SDT-EPC (=true) and cp-SDT-5GC (=true) may respectively indicate thewireless device is allowed to initiate the RA-based SDT for transmissionof CP data via the EPC and 5GC.

The wireless device may initiate an RA-based SDT on a cell when one ormore conditions are fulfilled. For example, the one or more conditionsmay be whether upper layer(s) request an establishment or resumption ofan RRC connection, whether the wireless device supports the SDT for aparticular type of data, whether one or more parameters (e.g., broadcastvia system information block(s)) indicate that the wireless device theRA-based SDT for the particular type of data when connected to aparticular type of network. For example, for cp-SDT when the wirelessdevice is connected to 5GC, the wireless device may initiate theRA-based SDT for the CP data based on at least one of upper layer(s)requesting an establishment or resumption of an RRC connection, CP-SDTavailable by the wireless device, and/or system information block(s)comprising cp-SDT-5GC = true.

For an SDT (e.g., RA-based SDT and/or CG-based SDT), the wireless devicemay determine a size of transport block (e.g., a size of messagecomprising uplink data). The transport block may comprise uplink data(e.g., associated with DTCH) that the wireless device transmits via theSDT. The transport block may comprise (e.g., further comprise) one ormore MAC headers, e.g., if required, and/or one or more MAC CEs, e.g.,if triggered. For example, the transport block that the wireless devicetransmits via the RA-based the SDT may be an MAC PDU that comprises theuplink data, the one or more MAC headers, and/or the one or more MACCEs.

A network or a base station may transmit (e.g., broadcast, multicast,and/or unicast) one or more message (e.g., system information block(s),RRC message(s), MAC CE(s), DCI(s) and/or any combination thereof)comprising one or more sdt-TBS values of a cell. For example, the one ormore sdt-TBS values may indicate an amount of uplink data (e.g.,associated with DTCH) that a wireless device transmits via an SDT (e.g.,RA-based SDT and/or CG-based SDT) on the cell. The wireless device thatreceives the one or more messages may determine, based on the one ormore sdt-TBS values, whether the wireless device initiates an SDT (e.g.,RA-based SDT and/or CG-based SDT) on the cell. The wireless device maydetermine a size of transport block comprising uplink data. The wirelessdevice may determine to transmit the uplink data via the SDT (orinitiate the SDT for transmission of the uplink data), e.g., if the sizeis smaller than or equal to at least one of the one or more sdt-TBSvalues. For example, the wireless device may be allowed to initiate theSDT on the cell for transmission of the uplink data, e.g., if the sizeis smaller than or equal to at least one of the one or more sdt-TBSvalues. The wireless device may determine not to transmit the uplinkdata via the SDT, e.g., if the size is larger than at least one of theone or more sdt-TBS values (e.g., larger than all of the one or moresdt-TBS values). For example, the wireless device may not be allowed toinitiate the RA-based SDT on the cell for transmission of the uplinkdata, e.g., if the size is larger than at least one of the one or moresdt-TBS values (e.g., larger than all of the one or sdt-TBS morevalues).

The one or more sdt-TBS values may indicate whether the wireless deviceinitiates the SDT (e.g., RA-based SDT and/or CG-based SDT) fortransmission of uplink data (e.g., associated with DTCH) or an RAprocedure to make a connection to the network or the base station. Forexample, the wireless device may determine to transmit the uplink datavia the SDT (or initiate the SDT for transmission of the uplink data),e.g., if the size is smaller than or equal to at least one of the one ormore sdt-TBS values. The wireless device may keep its RRC state as aNon-RRC_CONNECTED state while the RA-based SDT and/or after completingthe RA-based SDT. For example, the wireless device may determine not toperform (or initiate) the uplink data via the SDT, e.g., if the size islarger than at least one of the one or more sdt-TBS values (e.g., largerthan all of the one or more sdt-TBS values). In this case, the wirelessdevice may initiate the RA procedure to make the connection. Thewireless device may transmit the uplink data, e.g., after or in responseto determining that the RA procedure is successfully completed. Thewireless device may transition its RRC state from a Non-RRC_CONNECTEDstate to an RRC_CONNECTED state after or in response to determining thatthe RA procedure is successfully completed. For example, in this case,the wireless device may transmit the uplink data in the RRC_CONNECTEDstate.

A base station (or a network) may transmit (broadcast, multicast, and/orunicast) one or more messages (e.g., system information block(s), RRCmessage(s), MAC CE(s), DCI(s) and/or any combination thereof) comprisinga sdt-TBS value of a cell. The one or more messages may comprise ansdt-TBS value per an RA type of an RA procedure of the cell. Forexample, one or more RA types of the RA procedure may be available onthe cell. The one or more RA types may comprise a four-stepcontention-based RA procedure (e.g., FIG. 13A), a two-stepcontention-free RA procedure (e.g., FIG. 13A and/or FIG. 13B), and/or atow-step RA procedure (e.g., FIG. 13C). The sdt-TBS value may be acommon parameters applied to one or more RA types of the RA procedureconfigured on the cell. A wireless device that receives the one or moremessages may determine a particular RA type of RA procedure. Thewireless device may determine (e.g., select) a particular sdt-TBS valueof the particular RA type of RA procedure. The wireless device maydetermine, based on the particular sdt-TBS value, whether the wirelessdevice transmits uplink data (e.g., associated with DTCH) via an SDT(e.g., RA-based SDT and/or CG-based SDT). The SDT may use one or moreparameters (and/or procedures) of the particular RA procedure. Forexample, the wireless device may initiate, using the particular RAprocedure, the SDT on the cell, e.g., if a size of transport blockcomprising the uplink data (e.g., a size of message comprising theuplink data) is smaller than or equal to the particular sdt-TBS value.For example, the wireless device may not initiate, using the particularRA procedure, the RA-based SDT, e.g., if the size of transport block islarger than the particular sdt-TBS value. For example, the wirelessdevice may select a different RA type of RA procedure of the cell and/ormay initiate, using the different RA type of RA procedure, the RA-basedSDT, e.g., if the size of transport block is larger than the particularsdt-TBS value. For example, an sdt-TBS value of the different RA typemay be larger than the size of transport block.

An example configuration parameter of an sdt-TBS (e.g., or edt-TBS)value may be a value in bits. For example, an example format of thesdt-TBS value may be

sdt-TBS-r15  ENUMERATED   {b328, b408, b504, b600, b712, b808, b936,b1000or456},

where, for example, a value b328 may correspond to 328 bits, b408 maycorrespond to 408 bits and so on. For example, a value b1000or456 maycorrespond to 1000 bits for one or more first RA types of RA procedure,and 456 bits for one or more second RA types of RA procedure.

A base station (or a network) may transmit (e.g., broadcast, multicast,and/or unicast) one or more messages (e.g., system information block(s),RRC message(s), MAC CE(s), DCI(s) and/or any combination thereof)comprising one or more sdt-TBS values of a cell. The one or more sdt-TBSvalues may be per an RA type of an RA procedure of the cell. Forexample, one or more RA types of the RA procedure may be available onthe cell. The one or more RA types may comprise a four-stepcontention-based RA procedure (e.g., FIG. 13A), a two-stepcontention-free RA procedure (e.g., FIG. 13A and/or FIG. 13B), and/or atwo-step RA procedure (e.g., FIG. 13C). The one or more sdt-TBS valuesmay be a common parameters applied to one or more RA types of the RAprocedure configured on the cell. A wireless device that receives theone or more messages may determine a particular RA type of RA procedure.The wireless device may select a particular sdt-TBS value among the oneor more sdt-TBS values for the particular RA type of RA procedure. Theone or more messages may indicate that the one or more sdt-TBS valuesare configured for the particular RA type of RA procedure. The wirelessdevice may determine, based on the particular sdt-TBS value, whether thewireless device transmits uplink data (e.g., associated with DTCH) viaan SDT (e.g., RA-based SDT and/or CG-based SDT). The wireless device mayuse one or more parameters (and/or procedures) of the particular RAprocedure. For example, the wireless device may initiate, using theparticular RA procedure, the RA-based SDT on the cell, e.g., if a sizeof transport block comprising the uplink data (e.g., a size of messagecomprising the uplink data) is smaller than or equal to the particularsdt-TBS value. For example, the wireless device may not initiate, usingthe particular RA procedure, the RA-based SDT, e.g., if the size oftransport block is larger than the particular sdt-TBS value. Forexample, the wireless device may select a different RA type of RAprocedure of the cell and/or may initiate, using the different RA typeof RA procedure, the RA-based SDT, e.g., if the size of transport blockis larger than the particular sdt-TBS value. For example, an sdt-TBSvalue of the different RA type may be larger than the size of transportblock.

FIG. 18A illustrates an RA-based SDT with a four-step RA procedure asper an aspect of an example embodiment of the present disclosure. Awireless device may receive configuration parameters for the RA-basedSDT as per an aspect of an example embodiment of the present disclosure.The wireless device may initiate the four-step RA procedure for theRA-based SDT. The wireless device may determine to transmit a preamble(e.g., Msg1 1311 in FIG. 13A) via PRACH resource(s). The wireless devicemay determine the preamble and/or the PRACH resource(s) to indicate, toa base station, a request of a transmission of uplink data (e.g.,associated with DTCH) via Msg3 (e.g., Msg 3 1313 in FIG. 13B). Therequest may be an indication of triggering and/or initiating theRA-based SDT. The request may indicate a size (e.g., expected, measured,determined size) of a TB comprising the uplink data. The wireless devicemay receive a response (e.g., Msg2 1312 in FIG. 13A) to the preamble.The response may indicate whether the wireless device is allowed totransmit the uplink data via Msg 3 transmission. If the responseindicates that the wireless device is not allowed to transmit the uplinkdata, the wireless device may cancel the RA-based SDT. The wirelessdevice may transmit Msg3 without the uplink data, e.g., after or inresponse to canceling the RA-based SDT. If the response indicates thatthe wireless device is allowed to transmit the uplink data, the wirelessdevice transmit the TB comprising the uplink data via Msg3 transmission.The wireless device may receive a response (e.g., Msg 4 1314 in FIG.13A) to the Msg3 transmission.

FIG. 18B illustrates an RA-based SDT with a two-step RA procedure as peran aspect of an example embodiment of the present disclosure. A wirelessdevice may receive configuration parameters for the RA-based SDT as peran aspect of an example embodiment of the present disclosure. Thewireless device may initiate the two-step RA procedure for the RA-basedSDT. The wireless device may determine to transmit a preamble (e.g.,Preamble 1341 in FIG. 13C) via PRACH resource(s). The wireless devicemay determine to transmit a TB (e.g., Transport Block 1342 in FIG. 13C)comprising uplink data (e.g., associated with DTCH) via PUSCHresource(s). The wireless device may determine the preamble, the PRACHresource(s), and/or PUSCH resource(s) to indicate, to a base station, arequest of a transmission of uplink data via MsgA. The request may be anindication of triggering and/or initiating the RA-based SDT. The requestmay indicate a size (e.g., expected, measured, determined size) of theTB comprising the uplink data. The wireless device may receive aresponse (e.g., MsgB 1332 in FIG. 13C) to the MsgA. The response mayindicate a success (e.g., successRAR) of the MsgA transmission. Theresponse may indicate a fallback (e.g., fallbackRAR) to a contentionresolution of the four-step RA procedure. The wireless device may(re)transmit the TB via Msg 3 transmission of the contention resolution.The response may indicate that the wireless device is not allowed toperform the RA-based SDT. In this case, the wireless device may cancelthe RA-based SDT.

A wireless device may initiate an RA procedure on a cell fortransmission of uplink data (e.g., associated with DTCH) via an RA-basedSDT. The wireless device may select an RA type of the RA procedure amonga four-step RA type and a two-step RA type. The RA type may beassociated with at least one sdt-TBS value. The wireless device maydetermine a TBS of a TB based on the at least one sdt-TBS value. Forexample, the TB may comprise an MAC PDU that comprises the uplink dataand/or one or more padding bits. The wireless device may append the oneor more padding bits to the MAC PDU, e.g., if a size of the uplink data(e.g., expected message comprising the uplink data) is smaller than theTBS.

A wireless device may receive a message comprising one or moreconfigurations. A configuration of the one or more configuration maycomprise an identifier (or index) of the configuration. each of the oneor more configuration may comprise radio resource configurationparameters of one or more uplink radio resources that the wirelessdevice may use in a Non-RRC_CONNECTED state. For example, the wirelessdevice may perform a CG-based SDT via the one or more uplink radioresources.

A wireless device may receive an RRC message indicating one or moreuplink radio resources that a wireless device uses in aNon-RRC_CONNECTED state. For example, the wireless device may perform aCG-based SDT via the one or more uplink radio resources. The one or moreuplink radio resources in the Non-RRC_CONNECTED state may be one timeuse resource, e.g., for a single transmission. The one or more uplinkradio resources in the Non-RRC_CONNECTED state may be periodicresources, e.g., for one or more uplink transmission(s). The one or moreuplink radio resources in the Non-RRC_CONNECTED state may be referred toas a variety of names in different systems and/or implementations. Theone or more uplink radio resources in the Non-RRC_CONNECTED state may bereferred to as preconfigured uplink resources (PURs). Uplink grantsindicating the one or more uplink radio resources in theNon-RRC_CONNECTED state may be referred to as (pre-)configured grant(s).The (pre-)configured grant(s) may comprise a plurality of types. Forexample, the (pre-)configured grant(s) may comprise a (pre-)configuredgrant Type 1 and/or a (pre-)configured grant Type 2.

One or more uplink radio resources determined (and/or indicated) by the(pre-)configured grant Type 1 may not require an indication of(re-)initiating (and/or (re-)activating) the one or more uplink radioresources. For example, the one or more uplink radio resourcesdetermined (and/or indicated) by the (pre-)configured grant Type 1 maynot require an indication of (re-)initiating (and/or (re-)activating)the one or more uplink radio resources, e.g., after or in response toreceiving the RRC message indicating the one or more uplink radioresources in the Non-RRC_CONNECTED state.

For example, a wireless device may (re-)initiate (and/or (re-)activate)(pre-)configured grant Type 1 and/or one or more uplink radio resourcesindicated by the (pre-)configured grant Type 1 after or in response toreceiving the RRC message comprising the (pre-)configured grant Type 1.For example, For example, if a wireless device receives configurationparameters of the (pre)configured grant Type 1 for a Non-RRC_CONNECTEDstate, the wireless device may (re-)initiate (and/or (re-)activate)(pre-)configured grant Type 1 and/or one or more uplink radio resourcesindicated by the (pre-)configured grant Type 1 after or in response toreceiving the RRC message comprising the (pre-)configured grant Type 1and/or after or in response to transiting an RRC state of the wirelessdevice to the Non-RRC_CONNECTED state.

One or more uplink radio resources determined (and/or indicated) by(pre-)configured grant Type 2 may require an indication of(re-)initiating (and/or (re-)activating) the one or more uplink radioresources. For example, the wireless device may not (re-)initiate(and/or (re-)activate) the one or more uplink radio resources after orin response to receiving the RRC message comprising the (pre-)configuredgrant Type 2 that indicates the one or more uplink radio resources. Forexample, the wireless device may (re-)initiate (and/or (re-)activate)the one or more uplink radio resources after or in response to receivingthe indication of (re-)initiating (and/or (re-)activating) the one ormore uplink radio resources in the Non-RRC_CONNECTED state. The wirelessdevice may receive the indication after or in response to receiving theRRC message comprising the (pre-)configured grant Type 2 that indicatesthe one or more uplink radio resources. The wireless device may receivethe indication in the Non-RRC_CONNECTED state. If the wireless devicereceives the indication in an RRC_CONNECTED state, the wireless devicemay (re-)initiate (and/or (re-)activate) the one or more uplink radioresources after or in response to transitioning an RRC state of thewireless device to the Non-RRC_CONNECTED state. If the wireless devicereceives the indication in an RRC_CONNECTED state, the wireless devicemay (re-)initiate (and/or (re-)activate) the one or more uplink radioresources for the RRC_CONNECTED state. The wireless device may determineto (re-)initiate (and/or (re-)activate) and/or may keep the(re-)initiated (and/or (re-)activated) one or more uplink radioresources in the RRC_CONNECTED state as active in the Non-RRC_CONNECTEDafter or in response to transitioning an RRC state of the wirelessdevice to the Non-RRC_CONNECTED state. The uplink grant(s) indicatingthe one or more uplink radio resources in the Non-RRC_CONNECTED statemay be referred to as (pre-)configured grant(s) with a particular typeindicator, e.g., a (pre-)configured grant type 3, 4, or etc. Forexample, the (pre-)configured grant Type 1 and the (pre-)configuredgrant Type 2 may indicate one or more (periodic) uplink grants in theRRC_CONNECTED state. For example, the (pre-)configured grant Type 3(and/or other types of (pre-)configured grant) may indicate one or more(periodic) uplink grants in the Non-RRC_CONNECTED state.

A wireless device may receive, from a base station, one or moreconfiguration parameters that indicates and/or comprise a number ofoccasions of the one or more uplink radio resources (e.g., an exampleparameter name: NumOccasions). The one or more uplink radio resourcesmay be for a CG-based SDT. The number of occasions may indicate that theone or more uplink radio resources is one time use resource (or grant)for a single uplink transmission. The number of occasions may indicatethat the one or more uplink radio resources is a plurality of uplinkradio resources. The number of occasions may indicate that the one ormore uplink radio resources is one or more periodic radio resources.

The wireless device may receive the one or more configurationparameters, e.g., via a wireless device specific message (e.g., RRCmessage). The wireless device specific message may be an RRC releasemessage. The wireless device specific message may be an RRC message thatthe wireless device receives in an RRC_CONNECTED state.

In an example, the one or more configuration parameters that thewireless device receives may indicate a resource allocation of the oneor more uplink radio resources. For example, the one or moreconfiguration parameters may indicate a periodicity (e.g., exampleparameter name: Periodicity) of the one or more uplink radio resourcesin the Non-RRC_CONNECTED state. For example, the periodicity may be foruplink grant(s) of an SDT (e.g., CG-based SDT) and/or the one or moreuplink radio resources indicated by the uplink grant(s).

For example, the one or more configuration parameters may comprise atime offset. For example, the time offset may be for uplink grant(s) ofan SDT (e.g., CG-based SDT) and/or the one or more uplink radioresources indicated by the uplink grant(s). The time offset may be atime domain offset with respect to (and/or related to) a time reference.The time reference may be a particular SFN (e.g., of a H-SFN), aparticular subframe number, a particular slot number, a particularsymbol number, and/or a combination thereof. The time reference may bepredefined (e.g., SFN=0 and/or H-SFN = 0). The time reference may be apredefined value (e.g., SFN=0 and/or H-SFN=0), e.g., if a field of thetime reference is not present in the one or more configurationparameters. For example, the wireless device may receive the uplinkgrant(s), e.g., indicated by the one or more configuration parameters.The uplink grant(s) may indicate the one or more uplink radio resources.The one or more uplink radio resources may start from a symbol (of aslot of an SFN of a H-SFN) indicated by the time offset. The one or moreuplink radio resources may occur from the symbol periodically with theperiodicity. For example, the wireless device may, e.g., sequentially,determine that an N^(th) uplink grant of the one or more uplink grant(s)occurs in a transmission time interval (TTI, e.g., slot(s),mini-slot(s), symbol(s)) based on the time offset and N * Periodicity.The time offset may be defined in terms of a number of symbols, a numberof slots, a number of subframes, a number of SFNs, a number of H-SFNs,and/or a combination thereof. For example, the one or more configurationparameters may comprise a parameter, timeDomainOffset or the like. Forexample, timeDomainOffset indicates the time offset that the wirelessdevice received from a base station. For example, the one or moreconfiguration parameters may comprise a parameter, timeReferenceSFN orthe like (e.g., a time reference reference defined in terms of SFN(s)and/or H-SFN). For example, timeReferenceSFN indicates an SFN as thetime reference used for determination of the time offset of a resourcein time domain. For example, the SFN may repeat with a period of 1024frames. For example, the wireless device may receive, via SFN=3, the oneor more configuration parameters indicating timeReferenceSFN=0. Forexample, timeReferenceSFN=0 may indicate a time reference SFN=0 that is3 SFNs before the SFN=3. For example, timeReferenceSFN=0 may indicate atime reference SFN=0 that is 1021 SFNs after the SFN=3. For example, thewireless device may determine the closest SFN with the indicated numberpreceding the reception of the configured grant configuration. Forexample, in the above example, the wrieless device may determine thattimeReferenceSFN=0 indicates a time reference SFN=0 that is 3 SFNsbefore the SFN=3.

For example, the wireless device may, e.g., sequentially, determine thatthe N^(th) uplink grant of the uplink grant(s) occurs (and/or the uplinkgrant recurs) in the symbol for which: [(SFN × numberOfSlotsPerFrame ×numberOfSymbolsPerSlot) + (slot number in the frame ×numberOfSymbolsPerSlot) + symbol number in the slot] = (timeReferenceSFN× numberOfSlotsPerFrame × numberOfSymbolsPerSlot + timeDomainOffset ×numberOfSymbolsPerSlot + S + N × periodicity) modulo (1024 ×numberOfSlotsPerFrame × numberOfSymbolsPerSlot). For example,numberOfSlotsPerFrame is a number of slots in a frame. For example,numberOfSymbolsPerSlot, is a number of symbols in a slot. For example,periodicity is a peirodicity of the one or more uplink radio resourcesindicated by the one or more configuration parameters. For example, S isa symbol number (or symbol offset) indicated by the one or moreconfiguration parameters. The determination of the N^(th) uplink grantabove may be a case that (pre-)configured grant(s) may not require anadditional activation message (e.g., DCI, MAC CE, and/or RRC) thatactivates (and/or initiates) the one or more uplink radio resources(and/or (pre-)configured grant(s)).

For example, the wireless device may, e.g., sequentially, determine thatthe N^(th) uplink grant of the uplink grant(s) occurs (and/or the uplinkgrant recurs) in the symbol for which: [(SFN × numberOfSlotsPerFrame ×numberOfSymbolsPerSlot) + (slot number in the frame ×numberOfSymbolsPerSlot) + symbol number in the slot] = [(SFNstart time ×numberOfSlotsPerFrame × numberOfSymbolsPerSlot + slotstart time ×numberOfSymbolsPerSlot + symbolstart time) + N × periodicity] modulo(1024 × numberOfSlotsPerFrame × numberOfSymbolsPerSlot). Thedetermination of the N^(th) uplink grant above may be a case that(pre-)configured grant(s) may require an additional activation message(e.g., DCI, MAC CE, and/or RRC) that activates (and/or initiates) theone or more uplink radio resources (and/or (pre-)configured grant(s)).For example, SFNstart time, slotstart time, and symbolstart time are theSFN, slot, and symbol, respectively, at a time the one or more uplinkgrant(s) was (re-)initiated. For example, SFNstart time, slotstart time,and symbolstart time are the SFN, slot, and symbol, respectively, at atime where the wireless device receives an indication (e.g., DCI) of(re-)initiating (and/or (re-)activating) the one or more uplinkgrant(s). For example, SFNstart time, slotstart time, and symbolstarttime are the SFN, slot, and symbol, respectively, of a transmissionopportunity of PUSCH where the one or more uplink grant(s) was(re-)initiated. For example, the transmission opportunity of PUSCH isthe first opportunity of PUSCH where the one or more uplink grant(s) was(re-)initiated.

The wireless device may (re-)initiate transmission via one or moreuplink radio resources in the Non-RRC_CONNECTED state based on one ormore conditions. For example, the transmission may be a CG-based SDT.For example, the wireless device may receive configuration parameter(s)indicating the one or more conditions. For example, the wireless devicemay determine if a cell, where one or more uplink radio resources in theNon-RRC_CONNECTED state are configured, supports transmission(s) via theone or more uplink radio resources. For example, the wireless device mayreceive RRC message(s) (e.g., SIB). The RRC message(s) may compriseconfiguration parameter(s) indicating whether the cell supportstransmission(s) via the one or more uplink radio resources. Theconfiguration parameter(s) may indicate which type of transmission issupported (or available) via the one or more uplink radio resources. Forexample, the type may comprise control plane (CP) transmission and/oruser-plane (UP) transmission. The configuration parameter(s) mayindicate which type of network, the cell is connected, supports thetransmission via the one or more uplink radio resources. Depending onthe type of network that the cell is connected, the wireless device maydetermine whether the transmission via the one or more uplink radioresources is supported in the cell. For example, the type of network maycomprise one or more generations in a network system (e.g., 5G core,Evolved Packet Core (EPC), and/or the like) and/or one or more wirelesstechnologies (e.g., Wifi, 5G, Bluetooth, and/or the like). For example,the configuration parameter(s) may indicate which type of spectrum(and/or frequency band) supports the transmission via the one or moreuplink radio resources. For example, the type of spectrum may compriselicensed spectrum and/or unlicensed spectrum. For example, the type ofspectrum may comprise a CBRS (Citizens Broadband Radio Service) band(e.g., a wideband in 3.5 GHz band). For example, the type of spectrummay comprise a millimeter wave band (e.g., over 30 GHz band). Theconfiguration parameter(s) in the RRC message(s) may indicate acombination of the type of network, the type of spectrum, and/or thetype of transmission. For example, parameter(s), cp-PUR-5GC (e.g., theparameter value may be ‘true′/‘false’ or ‘enabled’/‘disabled’), in theRRC message(s) indicate whether CP transmission using CG-based SDT issupported in the cell when connected to 5G core network. For example,parameter(s), cp-PUR-EPC (e.g., the parameter value may be‘true’/‘false’ or ‘enabled’/‘disabled’), in the RRC message(s) indicatewhether CP transmission using CG-based SDT is supported in the cell whenconnected to EPC. For example, if the RRC message(s) received from acell indicates cp-PUR-EPC = ‘true’ (or ‘enabled’), the wireless devicedetermines that the CG-based SDT is supported in the cell when connectedto EPC.

FIG. 19A is an example of (pre-)configured grant(s) of one or moreuplink radio resources in a Non-RRC_CONNECTED state as per an aspect ofan embodiment of the present disclosure. A wireless device may perform aCG-based SDT via the one or more uplink radio resources of the(pre-)configured grant(s). The (pre-)configured grant(s) may not requirean additional activation message (e.g., DCI, MAC CE, and/or RRC) toactivate (and/or initiate) the one or more uplink radio resources(and/or (pre-)configured grant(s)). For example, a wireless device mayreceive an RRC message. The RRC message may comprise configurationparameters of the (pre-)configured grant(s) of a cell. The RRC messagemay comprise an indication and/or an index of a configuration comprisingthe configuration parameters. For example, the RRC message may be an RRCrelease message. After or in response to receiving the RRC message, thewireless device may determine (and/or store) the (pre-)configuredgrant(s) for the cell. After or in response to receiving the RRCmessage, the wireless device may (re-)initiate (or activate) the(pre-)configured grant. The one or more uplink radio resources (and/or(pre-)configured grant(s)) may be activated and/or initiated (or valid)in an RRC_INACTIVE state. For example, the wireless device may(re-)initiate (or activate) the (pre-)configured grant to start in(and/or from) a time reference. For example, the time reference may be asymbol, a slot, a subframe, an SFN, and/or a hyper-SFN (H-SFN). Forexample, the H-SFN comprise one or more SFNs (e.g., 1024 SFNs). Forexample, the time reference may be a combination of one or more of asymbol, a slot, a subframe, an SFN, and/or a hyper-SFN (H-SFN). Forexample, the time reference may be a symbol of a slot of an SFN of aH-SFN indicated by the configuration parameters (e.g., a time domainoffset (e.g., indicating the H-SFN, the SFN and/or the slot) and asymbol number S (e.g., indicating the symbol). For example, the wirelessdevice may determine that the (pre-)configured grant (re-)occurs with aperiodicity indicated by the configuration parameters.

In FIG. 19A, a wireless device may make a connection to a network (or abase station) via the CG-based SDT. For example, the wireless device maytransmit a first message via one or more uplink rando resources in aNon-RRC_CONNECTED state during the CG-based SDT. The first message maycomprise an RRC connection setup request (e.g., for the RRC connectionsetup procedure) and/or an RRC connection resume request (e.g., for theRRC connection resume procedure). The first message may comprise an SDT(EDT) request message. The wireless device may receive, from the basestation, a second message indicating a transition to an RRC_CONNECTEDstate. The second message may be a response to the first message. Forexample, the wireless device may receive an RRC connection setupmessage. For example, the wireless device may receive an RRC connectionresume message. The wireless device may transition to the RRC_CONNECTEDstate after or in response to receiving the second message. The wirelessdevice may deactivate and/or suspend (or clear), in an RRC_CONNECTEDstate, the one or more uplink radio resources (and/or (pre-)configuredgrant(s)) that were used in the Non-RRC_CONNECTED state. For example,the one or more uplink radio resources (and/or (pre-)configuredgrant(s)) may be deactivated and/or suspended (cleared, and/or invalid)after or in response to making the connection to the base station inFIG. 18A.

FIG. 19B is an example of (pre-)configured grant(s) indicating one ormore uplink radio resources in a Non-RRC_CONNECTED as per an aspect ofan embodiment of the present disclosure. A wireless device may perform aCG-based SDT via the one or more uplink radio resources of the(pre-)configured grant(s). The (pre-)configured grant(s) in FIG. 18B mayrequire an additional activation message (e.g., DCI, MAC CE, and/or RRC)that activates (and/or initiates) the one or more uplink radio resources(and/or (pre-)configured grant(s)). For example, a wireless device mayreceive an RRC message comprising configuration parameters of the(pre-)configured grant(s) of a cell. After or in response to receivingthe RRC message, the wireless device may determine (and/or store) the(pre-)configured grant(s) for the cell. For example, the RRC message maybe an RRC release message. After or in response to receiving the RRCmessage, the wireless device may not (re-)initiate (or activate) the(pre-)configured grant, e.g., until the wireless device receives theadditional activation message (e.g., DCI, MAC CE, and/or RRC). Thewireless device may monitor a PDCCH in the Non-RRC_CONNECTED state toreceive the additional activation message. The wireless device mayreceive the additional activation message (e.g., DCI, MAC CE, and/orRRC) after or in response to receiving the RRC message. A DCI carried bythe PDCCH may be the additional activation message. An MAC CE, and/orRRC message received based on a downlink assignment of a DCI carried bythe PDCCH may be the additional activation message. The configurationparameters in the RRC message may indicate time and frequency resourceallocation of the PDCCH, monitoring occasion(s) of the PDCCH, and/or amonitoring periodicity of the PDCCH. The wireless device may determinethat the (pre-)configured grant (re-)occurs with a periodicity indicatedby the configuration parameters and/or timing offset references (e.g., aH-SFN, a SFN, a slot and/or a symbol). For example, a wireless devicemay determine the SFN (e.g., of the H-SFN), the slot and/or the symbolbased on a reception timing of the additional activation messagereceived via the PDCCH. The wireless device may receive a deactivationmessage that indicates to deactivate and/or suspend (clear, and/orinvalidate) the one or more uplink radio resources (and/or(pre-)configured grant(s)). The wireless device may receive thedeactivation message in the Non-RRC_CONNECTED state.

In FIG. 19B, a wireless device may make a connection to a network (or abase station) via the CG-based SDT. For example, the wireless device maytransmit a first message via one or more uplink rando resources in aNon-RRC_CONNECTED state during the CG-based SDT. The first message maycomprise an RRC connection setup request (e.g., for the RRC connectionsetup procedure) and/or an RRC connection resume request (e.g., for theRRC connection resume procedure). The first message may comprise an SDT(EDT) request message. The wireless device may receive, from the basestation, a second message indicating a transition to an RRC_CONNECTEDstate. The second message may be a response to the first message. Forexample, the wireless device may receive an RRC connection setupmessage. For example, the wireless device may receive an RRC connectionresume message. The wireless device may transition to the RRC_CONNECTEDstate after or in response to receiving the second message. The wirelessdevice may deactivate and/or suspend (or clear), in an RRC_CONNECTEDstate, the one or more uplink radio resources (and/or (pre-)configuredgrant(s)) that were used in the Non-RRC_CONNECTED state. For example,the one or more uplink radio resources (and/or (pre-)configuredgrant(s)) may be deactivated and/or suspended (cleared, and/or invalid)after or in response to making the connection to the base station inFIG. 18B.

One or more radio resource(s) used for RA-based SDT and/or CG-based SDTmay be configured with a particular BWP of a cell. The particular BWPmay comprise a DL BWP and/or a UL BWP. One or more downlink receptionsof SDT may be configured in the DL BWP. One or more uplink transmissionof SDT may be configured in the UL BWP. The particular BWP may bereferred to as different name(s), e.g., as a contiguous (ornon-contiguous) frequency and/or a range of radio frequency where theRA-based SDT and/or CG-based SDT are configured. The particular BWP,where RA-based SDT and/or CG-based SDT are configured may be predefined(e.g., as an initial BWP of the cell). The particular BWP where RA-basedSDT and/or CG-based SDT are configured may be semi-staticallyconfigured, e.g., by an RRC message such as an RRC release message.

In an example, the wireless device may receive message(s) (e.g., RRCmessage(s)) comprising configuration parameters of the particular BWP.The particular BWP may comprise DL BWP and/or UL BWP. The configurationparameters may indicate a numerology (e.g., subcarrier spacing) used inthe particular BWP. The configuration parameters may indicate anumerology applied to the DL BWP and/or the UL BWP. The configurationparameters may comprise separate fields and/or indicators indicatingnumerologies, each used in DL BWP and/or UL BWP. The numerologies usedin DL BWP and/or UL BWP may be the same or different. The configurationparameters may comprise radio resource configuration parameters of DLand/or UL control channel (e.g., PDCCH and/or PUCCH) used fortransmission via the one or more radio resource(s). The configurationparameters may comprise radio resource configuration parameters of DLand/or UL data channel (e.g., PDSCH and/or PUSCH) used for transmissionvia the one or more radio resource(s). The DL control and/or datachannels (e.g., PDCCH and/or PDSCH) may be configured within the DL BWP.The UL control and/or data channels (e.g., PUCCH and/or PUSCH) may beconfigured within the UL BWP.

One or more radio resource(s) used for RA-based SDT and/or CG-based SDTmay be configured with a particular BWP of a cell. The particular BWPmay be an initial BWP. For example, at least one of a DL BWP and a ULBWP configured with RA-based SDT and/or CG-based SDT may be an initialBWP. For example, the DL BWP of the particular BWP may be an initial DLBWP. For example, the UL BWP of the particular BWP may be an initial ULBWP. For example, at least one of the DL BWP and the UL BWP may be aninitial BWP. For example, both of the DL BWP and the UL BWP may beinitial BWPs, e.g., the initial DL BWP and the initial UL BWP.

One or more radio resource(s) used for RA-based SDT and/or CG-based SDTmay be configured with a particular BWP of a cell. The particular BWPmay be configured separately from the initial BWP. For example, at leastone of a DL BWP and a UL BWP configured with RA-based SDT and/orCG-based SDT may be different from an initial BWP. For example, the DLBWP of the particular BWP may be different form the initial DL BWP. Forexample, the UL BWP of the particular BWP may be different from initialUL BWP. For example, the one or more radio resource(s) may be associatedwith a DL BWP and/or a UL BWP. For example, PDCCH (e.g., ACK, NACK,and/or fallback response(s) to the transmission via the one or moreradio resource(s)) and/or PDSCH (e.g., RRC response to the RRC messagetransmitted via the one or more radio resource(s)) related to thetransmission via the one or more radio resource(s) may be configuredwith the DL BWP. For example, PUCCH (e.g., ACK and/or NACK response tothe PDSCH) and/or PUSCH (e.g., data via the one or more radioresource(s)) related to the transmission via the one or more radioresource(s) may be configured with the UL BWP. The wireless device maydetermine that the particular BWP (e.g., DL BWP and/or UL BWP) is theinitial BWP (e.g., initial DL BWP and/or initial UL BWP, respectively),e.g., if field(s) indicating the configuration (e.g., frequencylocation, bandwidth, and/or numerology (e.g., subcarrier spacing)) ofthe particular BWP, e.g., that is different from the initial BWP, areabsent in the configuration parameters indicating the one or more radioresource(s).

One or more radio resource(s) used for RA-based SDT and/or CG-based SDTmay be configured with a particular BWP of a cell. The particular BWPmay be an active BWP that the wireless device used in RRC_CONNECTED. Forexample, the DL BWP of the particular BWP may be a last DL BWP that thewireless device used as an active DL BWP in an RRC_CONNECTED state. Forexample, the UL BWP of the particular BWP may be a last UL BWP that thewireless device used as an active UL BWP in RRC_CONNECTED. For example,the wireless device may transition to a Non-RRC_CONNECTED state from anRRC_CONNECTED state. A BWP (e.g., a last DL BWP and/or a last UL BWP)that the wireless device uses in the RRC_CONNECTED state may be used inthe transitioned the Non-RRC_CONNECTED state. The wireless device maydetermine that the particular BWP (e.g., DL BWP and/or UL BWP) is theBWP (e.g., the last DL BWP and/or the last UL BWP, respectively), e.g.,if field(s) indicating the configuration (e.g., frequency location,bandwidth, and/or numerology (e.g., subcarrier spacing)) of theparticular BWP, e.g., that is different from the last BWP, are absent inthe configuration parameters indicating the one or more radioresource(s).

One or more radio resource(s) used for RA-based SDT and/or CG-based SDTmay be configured with a particular BWP of a cell. The particular BWPmay be configured separately from the initial BWP. For example, the DLBWP of the particular BWP may be different form the initial DL BWP. Forexample, the UL BWP of the particular BWP may be different from initialUL BWP. For example, the one or more radio resource(s) may be associatedwith a DL BWP and/or a UL BWP. For example, PDCCH (e.g., ACK, NACK,and/or fallback response(s) to the transmission via the one or moreradio resource(s)) and/or PDSCH (e.g., RRC response to the RRC messagetransmitted via the one or more radio resource(s)) related to thetransmission via the one or more radio resource(s) may be configuredwith the DL BWP. For example, PUCCH (e.g., ACK and/or NACK response tothe PDSCH) and/or PUSCH (e.g., data via the one or more radioresource(s)) related to the transmission via the one or more radioresource(s) may be configured with the UL BWP.

In an example, the one or more configuration parameters may indicate avalue of a time alignment timer (TAT) (e.g., example parameter name:TimeAlignmentTimer) for a cell (and/or a cell group comprising the cell)where the one or more uplink radio resources in a Non-RRC_CONNECTEDstate are configured. The cell group comprising the cell may be referredto as a timing advance group (TAG). The value of the TAT may indicatehow long a timing advance offset value is valid (e.g., is valid to beused) for adjusting uplink timing for uplink transmission to the cell(and/or cell(s) in the cell group). For example, the value of the TATmay determine how long the wireless device determine the cell (and/orcell(s) belonging to the associated TAG) to be uplink time aligned. Thewireless device may determine (or adjust), based on the timing advanceoffset value, uplink timing for uplink transmission (e.g., PRACH, PUSCH,SRS, and/or PUCCH transmission) on the cell (and/or cells in the cellgroup). For example, the timing advance offset value may indicate howmuch (and/or long) the uplink timing for uplink transmission is delayedor advanced for uplink synchronization. For example, the wireless devicemay run the TAT during a time interval (and/or duration) indicated bythe value of the TAT. The wireless device may determine that the timingadvance offset value is valid (and/or is used) for adjusting uplinktiming for uplink transmission on the cell (or cell(s) in the cellgroup) while the TAT is running. The wireless device may determine thatan uplink from the wireless device to the cell (e.g., base station) isout-of-synchronized, e.g., if the TAT associated with the cell group(e.g., TAG) to which the cell belongs is not running and/or expires. Forexample, the wireless device may stop to perform uplink transmission(s)on a cell (and/or cell(s) in the cell group), e.g., if the TATassociated with the cell group (e.g., TAG) to which the cell belongs isnot running and/or expires. The wireless device may stop uplinktransmissions for a cell, e.g., due to the fact that the (e.g., maximum)uplink transmission timing difference between TAGs of the wirelessdevice or the (e.g., maximum) uplink transmission timing differencebetween TAGs of any MAC entity of the wireless device (e.g., two MACentities configured for a dual connectivity) is exceeded, the wirelessdevice may determine the TAT associated with the cell as expired. Thewireless device may perform a random access preamble (re-)transmissionand/or MSG A (re-)transmission, e.g., when the TAT associated with thecell group (e.g., TAG) to which the cell belongs is not running and/orexpires. The wireless device may (re-)start the TAT after or in responseto receiving a timing advance command that indicates a (new and/orupdated) timing advance offset value of the cell (and/or cells in thecell group). The timing advance command may be received as an MAC CEand/or DCI. The timing advance command may indicate a timing advanceoffset value of a cell where the one or more uplink radio resources in aNon-RRC_CONNECTED state.

The wireless device may (re-)start the time alignment timer after or inresponse to transition to a Non-RRC_CONNECTED, e.g., if the wirelessdevice receives (and/or is configured with) the one or more uplink radioresources for the Non-RRC_CONNECTED state. For example, the wirelessdevice may (re-)start the time alignment timer after or in response toreceiving configuration parameter(s) (e.g., timer value of the timealignment timer) associated with the time alignment timer. The wirelessdevice may (re-)start the time alignment timer after or in response toreceiving a timing advance offset value. The wireless device may receivea lower layer control message (e.g., DCI or PDCCH) that indicates thetiming advance offset value. The wireless device may receive an MAClayer control message (e.g., MAC CE and/or RAR) that indicates thetiming advance offset value. For example, the wireless device may(re-)start the time alignment timer after or in response to receiving atiming advance command MAC control element and/or PDCCH indicatingtiming advance adjustment. The wireless device may determine that thetiming advance offset value is valid at least while the TAT is running.The wireless device may validate a TA value based on one or morevalidation conditions. The wireless device may (re-)start the timealignment timer after or in response to a determination that the TA isvalidated. For example, if the TAT has run for a time interval (orduration) indicated by the value of the TAT, the wireless device maydetermine that the TAT expires. The wireless device may determine thatthe timing advance offset value is invalid in response to the expiry ofthe TAT.

Terminologies used in the present disclosure may be interchangeable withand/or be referred to as one or more different ones. For example, thetiming advance value may be referred to as a timing alignment value. Forexample, the timing advance offset value may be referred to as a timingalignment offset value. For example, the timing alignment timer may bereferred to as a time alignment timer, a timing advance timer, and/or atime advance timer. For example, the timing advance group may bereferred to as a timing alignment group.

For example, the wireless device determines, based on one or morevalidation conditions (e.g., a TAT based validation and/or a measruementbased validation), e.g., if the wireless device has a valid timingadvance value. For example, the wireless device may determine theconfiguration of the one or more uplink radio resources is valid, e.g.,based on configuration parameter(s) of the one or more uplink radioresources indicating a validity of the configuration. For example, thewireless device receives message(s) comprising the configurationparameter(s). the configuration is valid, e.g., if a field, config, inthe message(s) is set to setup (e.g., true). For example, theconfiguration is valid, e.g., if the field, config, is set to release(e.g., false).

The wireless device may determine, based on one or more validationconditions, if a timing advance value is valid or not for transmissionvia the one or more uplink radio resources in the Non-RRC_CONNECTEDstate. For example, the one or more validation conditions may comprise aTAT based validation and/or a measruement based validation. The wirelessdevice may determine to apply the configured condition(s) among the oneor more validation conditions. For example, the wireless device receivesmessage(s) comprising configuration parameters of a first validationcondition (e.g., the TAT based valditation) among the one or morevalidation conditions. The message(s) may not comprise configurationparameters of a second validation condition (e.g., the measuremetn basedvalidation) among the one or more validation conditions. In this case,the wireless device may determine if the timing advance value is validor not at least based on the first validation condition. For example, ifthe message(s) comprising configuration parameters of the firstvalidation condition (e.g., the TAT based valditation) and the secondvalidation condition (e.g., the measuremetn based validation), thewireless device may determine if the timing advance value is valid ornot at least based on the first validation condition and the secondvalidation condition.

For example, for the TAT based validation, the wireless device determinea validity of the timing advance value based on a TAT. The wirelessdevice may receive RRC message(s) comprising a value of the TAT. The TATmay be for a cell (and/or a TAG comprising the cell) where one or moreuplink radio resources in the Non-RRC_CONNECTED state are configured.The wireless device may determine that the timing advance value fortransmission via the one or more uplink radio resources is valid, e.g.,if the TAT is running. The wireless device may determine that thevalidation of the timing advance value for transmission is not at leastbased on the TAT, e.g., if the value of the TAT is not configured (e.g.,the RRC message(s) does not comprise the value of the TAT).

A wireless device may perform an SDT, followed by one or more subsequenttransmissions in a Non-RRC_CONNECTED state. The one or more subsequenttransmissions may comprise at least one uplink transmission. The one ormore subsequent transmissions may comprise at least one downlinkreception. For example, an SDT and one or more subsequent transmissionsmay be grouped together. For example, a group of transmission(s) maycomprise the SDT and/or the one or more subsequent transmission. The SDTmay be an initial uplink transmission of the group.

One or more subsequent transmissions may be one or more transmissionssubsequent to and/or associated with an SDT. For example, the wirelessdevice may transmit an uplink data (e.g., perform the SDT) via one ormore radio resource(s) in a Non-RRC_CONNECTED state. The wireless devicemay monitor, based on transmitting the uplink data, a PDCCH during atime window. The wireless device may receive, during the time window,DCI that schedules the one or more subsequent transmissions.

In an example, the wireless device may transmit an uplink data (e.g.,perform the SDT) via one or more radio resource(s) in aNon-RRC_CONNECTED state. The wireless device may monitor a PDCCH for aresponse to the uplink data. For example, the wireless device maymonitor, for the response, the PDCCH during a time window. The wirelessdevice may start the time window, e.g., after or in response totransmitting the uplink data. The wireless device may receive DCI viathe PDCCH during the time window. The DCI may be a response (e.g., ACKor NACK HARQ feedback) to the transmitting the uplink data. The DCI maycomprise an uplink grant (e.g., a dynamic grant) that schedules a firstsubsequent transmission (e.g., downlink or uplink transmission) of theone or more subsequent transmissions. For example, the first subsequenttransmission is a new uplink transmission. For example, the firstsubsequent transmission is a new downlink reception. For example, thefirst subsequent transmission may be a retransmission of the uplinkdata.

In an example, the wireless device may monitor, using one or more RNTIsand during the time window, the PDCCH for the response to thetransmission of the uplink data. The one or more RNTIs may comprise aC-RNTI of the wireless device. The one or more RNTIs may comprise anRNTI (e.g., CS-RNTI, PUR-RNTI, PUR C-RNTI, SDT-RNTI, and/or the like)assigned for the SDT. In the present disclosure, the RNTI assigned forthe SDT may be referred to as an SDT-RNTI.

The wireless device may receive (and/or detect), via the PDCCH, the DCIduring the time window. The DCI may comprise CRC parity bits scrambledwith the C-RNTI. The DCI comprising CRC parity bits scrambled with theC-RNTI may comprise a dynamic grant, e.g., dynamic uplink grantscheduling PUSCH and/or dynamic downlink assignment scheduling PDSCH.The DCI whose CRC parity bits scrambled with the C-RNTI may comprise anuplink grant that schedules a new UL transmission, e.g., in theNon-RRC_CONNECTED state. The DCI whose CRC parity bits scrambled withthe C-RNTI may comprise a downlink assignment that schedules a new DLtransmission, e.g., in the Non-RRC_CONNECTED state.

The wireless device may receive (and/or detect), via the PDCCH, the DCIduring the time window. The DCI may comprise CRC parity bits scrambledwith the SDT-RNTI. The DCI whose CRC parity bits scrambled with theSDT-RNTI may comprise an uplink grant that schedules a retransmission ofthe uplink data (and/or SDT), e.g., in the Non-RRC_CONNECTED state.

In an example, the wireless device may (re-)start the time window afteror in response to receiving the DCI. For example, the DCI may comprise aUL grant of a retransmission of the uplink data, a UL grant of new ULtransmission, and/or a DL assignment of a new DL transmission. Thewireless device may monitor, using at least one RNTI (e.g., C-RNTIand/or SDT-RNTI) and during the (re)started time window, the PDCCH. Thewireless device may receive a second DCI during the (re-)started timewindow via the PDCCH. The second DCI has CRC parity bits scrambled withthe SDT-RNTI and/or C-RNTI. The second DCI may comprise a UL grant of aretransmission of the uplink data, a UL grant of new UL transmission,and/or a DL assignment of a new DL transmission. The wireless device may(re-)start the time window after or in response to receiving the secondDCI and/or monitor, using the at least one RNTI (e.g., C-RNTI and/orSDT-RNTI), the PDCCH during the (re-)started time window. In thismanner, the wireless device may continue one or more subsequenttransmissions by (re-)starting the time window in response to receivingsuch DCI.

The wireless device may stop monitoring the PDCCH in response to anexpiry of the time window and/or the (re-)started time window. Thewireless device may stop the one or more subsequent transmissions in theNon-RRC_CONNECTED state, e.g., if the wireless device does not receiveDCI during the time window and/or the (re-)started time window. Forexample, the one or more subsequent transmissions associated with an SDTmay be one or more transmissions performed after or in response to theSDT (e.g., the first initial transmission) and before an expiry of thetime window (re-)started after or in response to the SDT. The wirelessdevice may stop monitoring, using one or more RNTIs, the PDCCH inresponse to an expiry of the time window and/or the (re-)started timewindow. The one or more RNTIs may comprise a C-RNTI of the wirelessdevice and/or RNTI(s) (e.g., CS-RNTI, PUR-RNTI, PUR C-RNTI, SDT-RNTI,and/or the like) assigned for the SDT.

FIG. 20 is an example of one or more subsequent transmissions of an SDTas per an aspect of an embodiment of the present disclosure. A wirelessdevice may receive a message (e.g., an RRC release message) comprisingand/or indicating configuration parameters of an SDT. The configurationparameters may indicate uplink grant(s) and/or one or more uplink radioresource(s) of the uplink grant(s) for the SDT. For example, the one ormore uplink radio resource(s) may comprise a first SDT resource, asecond SDT resource, and/or a third SDT resource in FIG. 20 . Thewireless device may transmit an uplink data via one of the one or moreuplink radio resource(s). The wireless device may skip a transmissionvia one of the one or more uplink radio resource(s), e.g., if there isno uplink data in a buffer of the wireless device. The one or moreuplink radio resource(s) may be a periodic resource with a periodicityas shown in FIG. 20 .

The wireless device may perform one or more subsequent transmissionsafter or in response to an SDT. For example, the SDT and the one or moresubsequent transmissions may be grouped together. For example, in FIG.20 , the wireless device may determine a first SDT resource, a secondSDT resource, and a third SDT resource. The wireless device may performa first initial transmission (e.g., an SDT) via the first SDT resource.The wireless device may start a time window in response to the firstinitial transmission. The wireless device may receive, via a PDCCH, oneor more DCIs that schedule one or more first subsequent transmissions.The wireless device may receive the one or more DCIs during the timewindow. The wireless device may receive the one or more DCIs during thetime window and/or the (re-)started time window one or more times basedon the present disclosure. The wireless device may stop monitoring thePDCCH in response to an expiry of the time window (or the (re-)startedtime window). The one or more subsequent transmissions may comprise atleast one uplink transmission (e.g., the one or more first subsequenttransmission in FIG. 20 ). The one or more subsequent transmissions maycomprise at least one downlink reception (e.g., the one or more secondsubsequent transmission in FIG. 20 ). The wireless device may notperform one or more subsequent transmissions (e.g., the third initialtransmission in FIG. 20 ).

A wireless device may perform, with a base station, a downlink and/oruplink beam management. The downlink and/or uplink beam management maycomprise a downlink and/or uplink beam measurement procedure,(re-)configuration of one or more beams (e.g., TCI states), a beam(e.g., TCI state) activation of the one or more beams, a beam selectionamong the one or more beams. For example, a TCI state may comprise a DLTCI state, spatial relation information (e.g., a UL TCI state). Thedownlink and/or uplink beam management may comprise a beam failuredetection and/or beam failure recovery procedures. The wireless devicemay perform the downlink beam management and the uplink beam managementseparately.

In the present disclosure, a wireless device may perform the downlink(e.g., PDSCH and/or PDCCH) and/or uplink beam management (e.g., PUSCH,PUCCH, and/or SRS) for transmission and/or reception in an RRC_CONNECTEDstate. In the present disclosure, a wireless device may perform thedownlink (e.g., PDSCH and/or PDCCH) and/or uplink (e.g., PUSCH, PUCCH,and/or SRS) beam management for transmission and/or reception in aNon-RRC_CONNECTED state (e.g., for an SDT and one or more subsequenttransmissions associated with the SDT).

An indicator of a reference signal in the downlink and/or uplink beammanagement may indicate a beam (e.g., TCI state, TX beam and/or RX beamof the wireless device) to use. For example, a wireless device mayreceive message(s) (e.g., RRC message(s), a RRC release message, and/orthe like) comprising configuration parameters of one or more radioresource(s). The configuration parameters may comprise indication(s)(e.g., indices) of one or more reference signals. The one or morereference signals may comprise an SSB identified by an SSBindex/identifier, a CSI-RS identified by a CSI-RS index/identifier(and/or CSI-RS resource index/identifier). The one or more referencesignals may comprise an SRS identified by an SRS index/identifier (e.g.,SRS resource index/identifier, SRS resource set index/identifier, and/ora combination thereof). The reference signal may represent and/orindicate a particular beam. For example, the SSB may represent and/orindicate a wide beam. For example, the CSI-RS may represent and/orindicate a narrow beam. For example, the SRS may represent and/orindicate a TX beam of the wireless device.

The configuration parameters in the message(s) may comprise indicator(s)indicating which reference signal(s) are associated with whichtransmission (e.g., PUSCH, PUCCH, and/or SRS) and/or reception (e.g.,PDCCH and/or PDSCH). A reference signal may be configured for radio linkmonitor, radio link recovery, and/or transmission and/or reception in anRRC_CONNECTED state and/or a Non-RRC_ CONNECTED state.

For example, the configuration parameters may comprise indicator(s)indicating which reference signal(s) are associated with data reception(e.g., PDSCH) and/or control signal (e.g., PDCCH) reception in aNon-RRC_CONNECTED state. For example, the data and/or the control signalmay be associated with the transmission via the one or more radioresource(s). For example, the reception may be for receiving a response(e.g., RRC response via PDSCH and/or L1 ACK/NACK/fallback via PDCCH) tothe transmission. For example, the indicator(s) may parameter(s) forconfiguring a QCL relationship between one or more DL reference signals(e.g., SSBs and/or CSI-RSs) and the DM-RS ports of the PDSCH, the DM-RSport of PDCCH, and/or the CSI-RS port(s) of a CSI-RS resource. Theparameter(s) may comprise one or more TCI states. Each of the one ormore TCI state may comprise at least one of following: one or more DLRS(s) (e.g., SSB(s), CSI-RS(s), and/or any combination thereof), cellindex/identifier, BWP index/identifier, and/or QCL relationship type(e.g., indicating the one or more large-scale properties). For example,the indicator(s) may be a TCI state of a particular channelconfiguration (e.g., PDSCH, PDCCH (e.g., CORESET)). For example, thePDSCH and/or PDCCH (e.g., CORESET) configuration may comprise at leastone of the one or more TCI states. For example, a TCI state of PDSCH mayindicate a QCL relationship between one or more DL reference signals(e.g., SSBs and/or CSI-RSs) and the DM-RS ports of the PDSCH. Thewireless device may determine RX beam(s) used to receive data via thePDSCH based on the TCI state (e.g., QCL relationship of the TCI state).For example, a TCI state of PDCCH may indicate a QCL relationshipbetween one or more DL reference signals (e.g., SSBs and/or CSI-RSs) andthe DM-RS ports of the PDCCH (e.g., CORESET). The wireless device maydetermine RX beam(s) used to receive control signal(s) via the PDCCHbased on the TCI state (e.g., QCL relationship of the TCI state).

A base station may transmit, to a wireless device, one or moremessage(s) to indicate a TCI state to be used for reception of PDSCHand/or PDCCH (e.g., CORESET). The one or more message(s) may comprise anRRC message, MAC CE, and/or DCI. At least one of the one or moremessage(s) may configure the TCI state for the PDSCH and/or PDCCH. Atleast one of the one or more message(s) may activate the TCI state forthe PDSCH and/or PDCCH. At least one of the one or more message(s) mayschedule the PDSCH and/or PDCCH based on the TCI state.

In an example, a wireless device may receive one or more message(s) that(re-)configures, updates, and/or activates the TCI state(s) of PDSCHand/or PDCCH (e.g., CORESET). For example, a first control message(e.g., an RRC message) of the one or more message(s) may indicate atleast one TCI state to be used for the PDSCH and/or PDCCH (e.g.,CORESET).

In an example, a wireless device may receive one or more message(s) that(re-)configures, updates, and/or activates the TCI state(s) of PDSCHand/or PDCCH (e.g., CORESET). For example, a first control message(e.g., an RRC message) of the one or more message(s) may indicate one ormore TCI states. A second control message (e.g., another RRC message, aDCI and/or MAC CE) of the one or more message(s) may indicate at leastone of the one or more TCI states to be used for the PDSCH and/or PDCCH(e.g., CORESET).

In an example, a wireless device may receive one or more message(s) that(re-)configures, updates, and/or activates the TCI state(s) of PDSCHand/or PDCCH (e.g., CORESET). For example, a first control message(e.g., an RRC message) of the one or more message(s) may indicate one ormore TCI states. A second control message (e.g., an RRC message, MAC CE,and/or DCI) of the one or more message(s) may indicate (or activate) atleast first one of the one or more TCI states. A third control message(e.g., an RRC message, MAC CE, and/or DCI) of the one or more message(s)may indicate at least second one of the at least first one of the one ormore TCI states to be used for the PDSCH and/or PDCCH (e.g., CORESET).

The wireless device may receive the configuration parameters comprisingindicator(s) indicating which reference signal(s) are associated withthe data (e.g., PUSCH) and/or control signal (e.g., PUCCH) transmissionassociated with the transmission via the one or more radio resource(s).

For example, the indicator(s) may comprise a spatial relationinformation (e.g., UL TCI state). The spatial relation information maybe for transmission(s) via PUSCH, PUCCH, and/or SRS. The wireless devicemay determine (e.g., identify) a particular spatial relation informationbased an index and/or identifier of the particular spatial relationinformation. The spatial relation information may indicate at least oneof following: cell index/identifier, one or more DL RSs (e.g., SSB(s),CSI-RS(s), and/or any combination thereof), SRS resourceindex/identifier, BWP index/identifier, pathloss reference RSindex/identifier, and/or power control parameter(s). The wireless devicemay determine antenna ports and/or precoder used for transmission(s) viaPUSCH and/or PUCCH based on the spatial relation information.

For example, the indicator(s) may be the spatial relation information(e.g., UL TCI state) of a particular channel configuration (e.g.,srs-spatial-relation-information for PUSCH and/orpucch-spatial-relation-information of PUCCH). For example, the PUSCHconfiguration may comprise at least one spatial relation information.For example, the PUCCH configuration may comprise at least one spatialrelation information. The spatial relation information of the PUSCH maybe different from the one of the PUCCH. The spatial relation informationof the PUSCH may be the same as the one of the PUCCH. The spatialrelation information(s) of the PUSCH and PUCCH may be configuredseparately and/or independently. There may be one or more spatialrelation information(s) applied to (and/or used for) the PUSCH and thePUCCH.

The wireless device may determine antenna ports and/or precoder used forthe PUSCH based on the spatial relation information of the PUSCH. Forexample, the wireless device receives message(s) comprisingconfiguration parameters of transmission via one or more radioresource(s) in an RRC_CONNECTED state and/or a Non-RRC_CONNECTED state.The configuration parameters (e.g., SRS resource indicator) may indicatean SRS resource of an SRS resource set. The SRS resource may comprisespatial relation information. The wireless device may determine, for thetransmission via the one or more radio resource(s), to use the sameantenna port(s) as the SRS port(s) of the SRS resource. The wirelessdevice may transmit, based on the determination, data via the one ormore radio resource(s) using the same antenna port(s).

For example, the wireless device may determine antenna ports and/orprecoder used for the PUCCH based on the spatial relation information ofthe PUCCH. For example, the wireless device receives message(s)comprising configuration parameters of PUCCH in an RRC_CONNECTED stateand/or a Non-RRC_CONNECTED state. The wireless device may transmituplink control signal(s) via the PUCCH for HARQ feedback (e.g., ACK orNACK) to PDSCH in the Non-RRC_CONNECTED state, for SR transmission(s),and/or measurement report(s). The configuration parameters (e.g., PUCCHspatial relation information) may indicate the spatial setting (e.g.,precoder and/or spatial domain filter) for PUCCH transmission and theparameters for PUCCH power control. The wireless device may determine,for the PUCCH transmission in the Non-RRC_CONNECTED state, a spatialdomain filter used for a reception of a DL RS indicated by the spatialrelation information. For example, if the spatial relation informationfor the PUCCH comprises an SSB index/identifier of an SSB, the wirelessdevice may transmit the PUCCH using a same spatial domain filter as fora reception of the SSB for a cell. For example, if the spatial relationinformation for the PUCCH comprises a CSI-RS index/identifier (e.g.,NZP-CSI-RS resource index/identifier) of a CSI-RS, the wireless devicemay transmit the PUCCH using a same spatial domain filter as for areception of the CSI-RS for a cell. For example, if the spatial relationinformation for the PUCCH comprises an SRS index/identifier of an SRS(e.g., SRS resource), the wireless device may transmit the PUCCH using asame spatial domain filter as for a transmission of the SRS for a celland/or UL BWP.

A base station may transmit, to a wireless device, one or moremessage(s) to indicate spatial relation information (e.g., UL TCI state)to be used for transmission of PUSCH, PUCCH, and/or SRS. The one or moremessage(s) may comprise an RRC message, MAC CE, and/or DCI. At least oneof the one or more message(s) may configure the spatial relationinformation (e.g., UL TCI state) for the PUSCH, PUCCH, and/or SRS. Atleast one of the one or more message(s) may activate the spatialrelation information (e.g., UL TCI state) for the PUSCH, PUCCH, and/orSRS. At least one of the one or more message(s) may schedule the PUSCH,PUCCH, and/or SRS based on the spatial relation information (e.g., ULTCI state).

In an example, a wireless device may receive one or more message(s) that(re-)configures, updates, and/or activates the spatial relationinformation of PUSCH, PUCCH, and/or SRS. For example, a first controlmessage (e.g., an RRC message) of the one or more message(s) mayindicate at least one spatial relation information (e.g., UL TCI state)to be used for the PUSCH, PUCCH, and/or SRS.

In an example, a wireless device may receive one or more message(s) that(re-)configures, updates, and/or activates the spatial relationinformation of PUSCH, PUCCH, and/or SRS. For example, a first controlmessage (e.g., an RRC message) of the one or more message(s) mayindicate one or more spatial relation information(s) (e.g., UL TCIstate(s)). A second control message (e.g., another RRC message, a DCIand/or MAC CE) of the one or more message(s) may indicate at least oneof the one or more spatial relation information(s) to be used for thePUSCH, PUCCH, and/or SRS.

In an example, a wireless device may receive one or more message(s) that(re-)configures, updates, and/or activates the spatial relationinformation of PUSCH, PUCCH, and/or SRS. For example, a first controlmessage (e.g., an RRC message) of the one or more message(s) mayindicate one or more spatial relation information(s) (e.g., UL TCIstate(s)). A second control message (e.g., an RRC message, MAC CE,and/or DCI) of the one or more message(s) may indicate (or activate) atleast first one of the one or more spatial relation information(s). Athird control message (e.g., an RRC message, MAC CE, and/or DCI) of theone or more message(s) may indicate at least second one of the at leastfirst one of the one or more spatial relation information(s) to be usedfor the PUSCH, PUCCH, and/or SRS.

FIG. 21 is an example of beam management for transmission and/orreception in a Non-RRC_CONNECTED state as per an aspect of an embodimentof the present disclosure. The wireless device may receive message(s)comprising configuration parameters of transmission/reception in theNon-RRC_CONNECTED state. The configuration parameters may indicateconfigurations of radio resources of PUSCH, PDCCH, PDSCH, and/or PUCCHused in the Non-RRC_CONNECTED state. The configuration parameters mayindicate one or more radio resource(s) for uplink transmission (e.g.,via PUSCH) in the Non-RRC_CONNECTED state. The configuration parametersmay indicate which beam(s) (e.g., reference signal(s)) are used totransmit (e.g., via PUSCH and/or PUCCH) or receive (e.g., via PDSCHand/or PDCCH) in the Non-RRC_CONNECTED state. For example, in FIG. 22 ,the wireless device transmits, using the 1st beam, data via one or moreradio resource(s) in the Non-RRC_CONNECTED state. The wireless devicemay start to monitor PDCCH using the 3rd beam. The wireless device mayreceive, via the PDCCH, DCI that comprise downlink assignment of PDSCH.The wireless device may receive the PDSCH using the 4th beam. Thewireless device may transmit, via PUCCH, an HARQ feedback (e.g., ACK orNACK) using the 2nd beam. The base station may receive or transmit datausing different beams and/or a same beam, e.g., the 1st beam for PUSCHreception, the 2nd beam for PDCCH transmission, the 3rd beam for PDSCHtransmission, and/or the 4th beam for PUCCH reception. The wirelessdevice may receive second message(s) (e.g., RRC message, MAC CE, DCI,and/or a combination thereof) reconfigure, change, activate/deactivate,and/or update the beam configuration of the PUSCH, PDCCH, PDSCH, and/orPUCCH.

In multi-beam operations, a cell may transmit one or more DL RSs (e.g.,a plurality of SSBs, CSI/RS, and/or the like), e.g., using one or morebeams (e.g., TX beams of the cell). For example, each of the one or morebeam may be associated with at least one of the one or more DL RSs. Forexample, each of channel(s) (e.g., the PDCCH, PDSCH, PUSCH and/or PUCCH)for transmission and/or reception of the cell may be associated with atleast one of the one or more beams (e.g., at least one of the one ormore DL RSs).

For example, a wireless device may receive message(s) (e.g., RRCmessage, MAC CE, DCI, and/or any combination thereof) comprising radioresource configuration parameters indicating which beam is associatedwith which channel(s) (e.g., the PDCCH, PDSCH, PUSCH and/or PUCCH). Forexample, the radio resource configuration parameters may indicate that abeam configuration, e.g., TCI state (and/or DL TCI state) and/or spatialrelation information (and/or UL TCI state), of the channel(s) comprisesa first DL RS of the plurality of DL RSs. The first DL RS may representand/or indicate the first beam (e.g., as shown in FIG. 21 ). Forexample, one of the plurality of DL RS may be associated with one ormore channels (e.g., the PDCCH, PDSCH, PUSCH, and/or PUCCH). Thewireless device may determine, based on the association, antenna port(s)and/or precoder (e.g., spatial domain filter) to be used for thetransmission and/or the reception performed via the channel(s). Forexample, the wireless device may determine the antenna port(s) and/orthe precoder (e.g., spatial domain filter) based on one(s) that used forreceiving the first DL RS.

For an SDT, a wireless device may receive, from a base station, amessage indicating one or more DL RSs (e.g., a plurality of SSBs,CSI/RS, and/or the like), e.g., using one or more beams (e.g., TX beamsof the cell). The wireless device may determine, based on at least oneof the one or more DL RSs, transmission parameters (e.g., TX antennaparameters) of a wireless device for PUSCH, PUCCH, and/or SRS. Thewireless device may determine, based on at least one of the one or moreDL RSs, reception parameters (e.g., RX antenna parameters) of a wirelessdevice for PDSCH, and/or PDCCH.

In an example, the message that the wireless device for the SDT mayindicate a DL RS (e.g., an SSBs, CSI/RS, and/or the like) to be used forPDCCH, PDSCH, PUSCH, PUCCH, and/or SRS. In an example, the message mayindicate a first DL RS (e.g., an SSBs, CSI/RS, and/or the like) for anuplink transmission, e.g., PUSCH, PUCCH, and/or SRS. In an example, themessage may indicate a second DL RS (e.g., an SSBs, CSI/RS, and/or thelike) for a downlink reception, e.g., PDCCH, and/or PDSCH. In anexample, the message may indicate one or more DL RSs (e.g., an SSBs,CSI/RS, and/or the like), each DL RS is dedicated a particular channelof PDCCH, PDSCH, PUSCH, PUCCH, and/or SRS. A DL RS indicated by themessage for a first channel (e.g., PDCCH, PDSCH, PUSCH, PUCCH, and/orSRS) may be the same to a DL RS indicated by the message for a secondchannel (e.g., PDCCH, PDSCH, PUSCH, PUCCH, and/or SRS). A DL RSindicated by the message for a first channel (e.g., PDCCH, PDSCH, PUSCH,PUCCH, and/or SRS) may be different from a DL RS indicated by themessage for a second channel (e.g., PDCCH, PDSCH, PUSCH, PUCCH, and/orSRS).

For an SDT, a wireless device may receive, from a base station, amessage indicating one or more DL RSs (e.g., a plurality of SSBs,CSI/RS, and/or the like), e.g., using one or more beams (e.g., TX beamsof the cell). The wireless device may select at least one of the one ormore DL RSs. Th wireless device may select the at least one to determinetransmission parameters (e.g., TX antenna parameters) of a wirelessdevice for PUSCH, PUCCH, and/or SRS. The wireless device may select atleast one of the one or more DL RSs to determine reception parameters(e.g., RX antenna parameters) of a wireless device for PDSCH, and/orPDCCH.

In an example, the message that the wireless device for the SDT mayindicate one or more DL RSs (e.g., one or more SSBs, CSI/RSs, and/or thelike) to be used for PDCCH, PDSCH, PUSCH, PUCCH, and/or SRS. Thewireless device may select at least one of the one or more DL RSs forthe SDT. For example, the wireless device may initiate the SDT, e.g., inresponse to an uplink data available in a buffer and/or in response toan uplink grant (or an uplink radio resource of the uplink grant)available for the SDT. The wireless device may determine or select theat least one of the one or more DL RSs for the PDCCH, PDSCH, PUSCH,PUCCH, and/or SRS of the SDT.

The determination and/or the selection of the at least one may be basedon measurements (e.g., RSRP values) of the one or more DL RSs. Forexample, the message may comprise and/or indicate a power thresholdvalue. The wireless device may measure RSRPs of the one or more DL RSs.For example, the wireless device may select the at least one based on anRSRP value of the at least one being larger than the power thresholdvalue. For example, the wireless device may select the at least onebased on an RSRP value of the at least one being the largest one amongthe RSRP values of the one or more DL RSs.

The wireless device may select at least one of the one or more DL RSs tobe used for PUSCH of an SDT (and/or one or more subsequent transmissionsof the SDT). The wireless device may determine, based on the at leastone, a configuration of the PUSCH of the SDT and/or uplink radioresource(s) of the PUSCH of the SDT. For example, the wireless devicemay receive a message comprising a set of the uplink radio resource(s).The message may comprise a configuration comprising the set of theuplink radio resource(s). The message may comprise one or moreconfigurations. Each of the one or more configuration may comprise oneof the uplink radio resource(s). The message may indicate that each ofthe uplink radio resource(s) is associated with one of the one or moreDL RSs. The wireless device may select a first uplink grant (and/or afirst uplink radio resource(s) among the set of the uplink radioresource(s), e.g., if the message indicates the first uplink grant(and/or the first uplink radio resource(s)) is associated with the atleast one of the one or more DL RSs. The wireless device may transmit anuplink data (via CG-based SDT and/or RA-based SDT) using antennaconfiguration(s) (e.g., spatial relation information, and/or UL TCIstate) of the at least one of the one or more DL RSs.

In the same way, the wireless device may determine, for an SDT and/orits one or more subsequent transmissions, uplink radio resource(s) forPUCCH and/or SRS based on a selection of one of the one or more DL RSs.For example, the wireless device may receive a message indicating one ormore radio resource(s) for PUCCH and/or SRS. The one or more radioresource(s) may be a particular DL RS specific. For example, thewireless device may select the one of the one or more DL RSs based onRSRPs of the one or more DL RSs. For example, an RSRP value of the onemay be larger than a power threshold. For example, the RSRP value may bethe largest one among the RSRP values of the one or more DL RSs. Forexample, a first DL RS of the one or more DL RSs may be configured,e.g., as spatial relation information (and/or UL TCI state) of a firstradio resource(s) of the one or more radio resource(s). The wirelessdevice may determine (and/or select), for a transmission via a firstchannel (e.g., PUSCH), a DL RS (e.g., spatial relation informationand/or UL TCI state) of the one or more DL RS as the one for atransmission via a second channel (e.g., PUCCH and/or SRS) oftransmission. The wireless device may determine (and/or select) a DL RS(e.g., spatial relation information and/or UL TCI state) of the one ormore DL RS per a transmission channel (e.g., PUSCH, PUCCH, and/or SRS).

A wireless device may select at least one of the one or more DL RSs tobe used for PDCCH (e.g., CORESET) of an SDT (and/or one or moresubsequent transmissions of the SDT). The wireless device may determine,based on the at least one, a configuration of the PDCCH (e.g., CORESETof the PDCCH) of the SDT and/or downlink radio resource(s) of the PDCCHof the SDT. For example, the wireless device may receive a messagecomprising a set of the downlink radio resource(s) (e.g., CORESET(s)) ofdownlink control channels. The message may comprise a configurationcomprising the set of the downlink radio resource(s) (e.g., CORESET(s)).The message may comprise one or more configurations. Each of the one ormore configuration may comprise one of the downlink radio resource(s)(e.g., CORESET(s)). The message may indicate that each of the downlinkradio resource(s) is associated with one of the one or more DL RSs.Association between each of the downlink radio resource(s) and the oneor more DL RSs may be predefined. For example, the wireless device mayselect at least one of the one or more DL RSs, e.g., based on RSRPvalues of the one or more DL RSs. An RSRP value of the at least one maybe larger than a power threshold value. the RSRP value of the at leastone may be the largest one among the RSRP values. The wireless devicemay select a first downlink radio resource (e.g., CORESET) among the setof the downlink radio resource(s) (e.g., CORESET(s)), e.g., if the firstdownlink radio resource (e.g., CORESET) is associated with the at leastone of the one or more DL RSs. The wireless device may receive controlsignal (e.g., DCI) via the first downlink radio resource (via CG-basedSDT and/or RA-based SDT) using antenna configuration(s) (e.g., TCIstate) of the at least one of the one or more DL RSs.

In the same way, the wireless device may determine, for an SDT and/orits one or more subsequent transmissions, downlink radio resource(s) forPDSCH based on a selection of one of the one or more DL RSs. Forexample, the wireless device may receive a message indicating one ormore radio resource(s) for PDSCH. The one or more radio resource(s) maybe a particular DL RS specific. For example, the wireless device mayselect the one of the one or more DL RSs based on RSRPs of the one ormore DL RSs. For example, an RSRP value of the one may be larger than apower threshold. For example, the RSRP value may be the largest oneamong the RSRP values of the one or more DL RSs. For example, a first DLRS of the one or more DL RSs may be configured, e.g., as DL TCI state ofa first radio resource(s) of the one or more radio resource(s). Thewireless device may determine (and/or select), for a reception via afirst channel (e.g., PDCCH), a DL RS (e.g., DL TCI state) of the one ormore DL RS as the one for a reception via a second channel (e.g., PDSCH)of transmission. The wireless device may determine (and/or select) a DLRS (e.g., DL TCI state) of the one or more DL RS per a transmissionchannel (e.g., PDCCH and/or PDSCH).

The wireless device may determine (and/or select), for a reception viaone or more channels (e.g., PDCCH and/or PDSCH), a DL RS (e.g., DL TCIstate) of the one or more DL RS as the one for a reception via a secondchannel (e.g., PDSCH) of transmission. The wireless device may determine(and/or select) a DL RS (e.g., spatial relation information and/or ULTCI state) of the one or more DL RS per a transmission channel (e.g.,PDCCH and/or PDSCH).

The wireless device may determine (and/or select) a DL RS of the one ormore DL RS (e.g., a DL RS of spatial relation information) configuredand/or selected for a transmission (e.g., PUSCH via an SDT) as the one(e.g., a DL RS of a DL TCI state) for a reception via one or morechannels (e.g., PDCCH and/or PDSCH) of transmission. For example, thewireless device may select, e.g., based on RSRPs of the one or more DLRS, the DL RS for uplink transmission of the SDT and/or its associatedone or more subsequent transmissions. The wireless device may use the DLRS for the reception of the PDCCH and/or PDSCH. For example, thewireless device may determine that DM-RS antenna port(s) associated withPDCCH reception and/or the PDSCH receptions is quasi co-located with theDL RS (e.g., SS/PBCH block and/or the CSI-RS resource) that the wirelessdevice determines and/or selects for the uplink transmission of the SDTand/or its associated one or more subsequent transmissions

A wireless device may monitor, e.g., in an RRC_CONNECTED state, a set ofPDCCH candidates in one or more CORESETs on an active DL BWP on aserving cell (e.g., each activated serving cell) configured with PDCCHmonitoring. The active DL BWP may be a first active DL BWP and/or aninitial DL BWP. The active DL BWP may be a DL BWP where the wirelessdevice transition to the RRC_CONNECTED state from a Non-RRC_CONNECTED,e.g., via an SDT. For example, a message that the wireless devicereceives during the SDT may indicate a transition to the RRC_CONNECTEDstate and indicate the DL BWP as the first active BWP in theRRC_CONNECTED state. The monitoring the set of PDCCH candidates in theone or more CORESETs may be based on corresponding search space sets.The monitoring may be referred to as decoding each PDCCH candidate basedon the monitored DCI formats. In the present disclosure, monitoringPDCCH may be decoding PDCCH candidate(s) based on monitored DCIformat(s). In the present disclosure, receiving, via PDCCH, DCI may bedetecting and/or receiving the DCI with one of the monitored DCIformat(s) based on decoding, with the monitored DCI format(s), PDCCHcandidates comprising the PDCCH.

For example, a set of PDCCH candidates for a wireless device to monitormay be defined in terms of PDCCH search space set(s). A search space setmay be a common search space (CSS) set and/or a wireless specific searchspace set that may be referred to as a UE-specific search space (USS)set.

A wireless device may monitor PDCCH candidates in one or more of thefollowing search spaces sets: a Type0-PDCCH CSS set for receiving MIBand/or SIB; a Type0A-PDCCH CSS set for receiving other systeminformation; a Type1-PDCCH CSS set for a random access procedure; aType2-PDCCH CSS set for a paging procedure; a Type3-PDCCH CSS forreceiving group common information (e.g., DCI), one or more USS set forthe wireless device.

For example, a Type0-PDCCH CSS set may be configured by pdcch-ConfigSIB1in MIB or by searchSpaceSIB1 in PDCCH-ConfigCommon or by searchSpaceZeroin PDCCH-ConfigCommon for a DCI format with CRC scrambled by a SI-RNTI,e.g., on a cell (e.g., a primary cell of an MCG). A Type0A-PDCCH CSS setmay be configured by searchSpaceOtherSystemInformation inPDCCH-ConfigCommon for a DCI format with CRC scrambled by a SI-RNTI,e.g., on a cell (e.g., a primary cell of an MCG). A Type1-PDCCH CSS setmay be configured by ra-SearchSpace in PDCCH-ConfigCommon for a DCIformat with CRC scrambled by a RA-RNTI, a MsgB-RNTI, or a TC-RNTI, e.g.,on a cell (e.g., a primary cell of an MCG). A Type2-PDCCH CSS set may beconfigured by pagingSearchSpace in PDCCH-ConfigCommon for a DCI formatwith CRC scrambled by a P-RNTI, e.g., on a cell (e.g., a primary cell ofan MCG). A Type3-PDCCH CSS set may be configured by SearchSpace inPDCCH-Config with searchSpaceType = common for DCI formats with CRCscrambled by INT-RNTI, SFI-RNTI, TPC-PUSCH-RNTI, TPC-PUCCH-RNTI,TPC-SRS-RNTI, or CI-RNTI and, e.g., for a cell (e.g., a primary cell),C-RNTI, MCS-C-RNTI, CS-RNTI(s), or PS-RNTI. A USS set may be configuredby SearchSpace in PDCCH-Config with searchSpaceType = ue-Specific forDCI formats with CRC scrambled by C-RNTI, MCS-C-RNTI, SP-CSI-RNTI,CS-RNTI(s), SL-RNTI, SL-CS-RNTI, or SL-L-CS-RNTI.

A wireless device may determine a DL RS for downlink reception(s) (e.g.,PDSCH, PDCCH and/or CORESET of the PDCCH) in an RRC_CONNECTED state. Forexample, the wireless device may use the DL RS to determine antennaconfiguration parameters (e.g., DM-RS antenna port) associated with thedownlink reception(s). For example, the wireless device may determinethat DM-RS antenna port(s) associated with the downlink receptions isquasi co-located with the SS/PBCH block or the CSI-RS resource of the DLRS.

In existing technologies, a wireless device may determine, based on aninitial access procedure (an MIB (or SIB) reception/acquisition) and/ora random access procedure, a DL RS for downlink reception(s) (e.g.,PDCCH and/or PDSCH) in an RRC_CONNECTED state. For example, the wirelessdevice may use the DL RS to determine antenna configuration parametersof the downlink reception(s).

In an example, in the existing technologies, the wireless device in theRRC_CONNECTED state may not receive, from a base station, configurationparameters and/or an activation indication for downlink reception(s)(e.g., PDCCH and/or PDSCH). For example, the configuration parametersmay comprise antenna configuration parameters of one or more TCIstate(s) for the downlink reception(s). The configuration parameters mayactivate at least one of the one or more TCI state(s). For example, theactivation indication may activate at least one of the one or more TCIstate(s). For example, if the wireless device in the RRC_CONNECTED statedoes not receive, from a base station, the configuration parametersand/or the activation indication, the wireless device may determine,based on an initial access procedure (an MIB (or SIB)reception/acquisition) and/or a random access procedure, a DL RS fordownlink reception(s) (e.g., PDCCH and/or PDSCH) in an RRC_CONNECTEDstate. For example,

In an example, there may be one or more example cases that the wirelessdevice determines, based on an initial access procedure (an MIB (or SIB)reception/acquisition) and/or a random access procedure, a DL RS fordownlink reception(s) (e.g., PDCCH and/or PDSCH) in an RRC_CONNECTEDstate. For example, the one or more example cases comprise a case that awireless device may not receive, from a base station a configuration ofmore than one TCI states (e.g., by tci-StatesPDCCH-ToAddList andtci-StatesPDCCH-ToReleaseList) for a CORESET. For example, the one ormore example cases comprise a case that a wireless device may receive,from a base station a configuration of more than one TCI states, and maynot receive an activation command (e.g., MAC CE activation commandand/or DCI based activation command) for one of the TCI states. For thecase(s) comprising the one or more example cases, the wireless devicemay determine that DM-RS antenna port(s) associated with PDCCHreceptions is quasi co-located with the SS/PBCH block or the CSI-RSresource the wireless device identifies during an initial accessprocedure (an MIB (or SIB) reception/acquisition) and/or a random accessprocedure.

FIG. 22 is an example of a determination of at least one RS fortransmission(s) in an RRC_CONNECTED state. A wireless device may receiveone or more reference signals (RSs). The one or more RSs may comprise aDL RS such as an SSB and/or CSI-RS. The wireless device may select atleast one RS among the one or more RSs during a random access, during aninitial access, and/or during MIB/SIB acquisition. The wireless devicemay perform transmission(s) in an RRC_CONNECTED state. The wireless maydetermine antenna port(s) associated with the transmission(s) (e.g.,PDCCH and/or PDSCH reception) in the RRC_CONNECTED state based on the atleast one RS. For example, the wireless device may determine that DM-RSantenna port(s) associated with PDCCH receptions in the RRC_CONNECTEDstate is quasi co-located with the at least one RS (e.g., SS/PBCH blockof the at least one RS and/or CSI-RS resource of the at least one RS).

A problem arises when a wireless device transitions to an RRC_CONNECTEDstate via an SDT and/or its associated one or more subsequenttransmissions. In this case, the wireless device may transition to theRRC_CONNECTED state without performing an initial access procedure (anMIB (or SIB) reception/acquisition) and/or a random access procedure.For example, the wireless device may transition to the RRC_CONNECTEDstate in response to a message (e.g., RRC message, RRC setup message,and/or RRC resume message) received during the SDT and/or its associatedone or more subsequent transmissions. The wireless device may performthe initial access procedure (an MIB (or SIB) reception/acquisition)and/or perform the random access procedure, e.g., before the SDT and/orits associated one or more subsequent transmissions. For example, theSS/PBCH block or the CSI-RS resource that the wireless device identifiesduring the initial access procedure (an MIB (or SIB)reception/acquisition) and/or the random access procedure may beoutdated to use for a determination of DM-RS antenna port(s) associatedwith PDCCH reception in the RRC_CONNECTED state. The determination ofDM-RS antenna port(s) associated with the PDCCH receptions based on theSS/PBCH block or the CSI-RS resource may result in a performancedegradation in transmission and/or reception performed in theRRC_CONNECTED state. There is a need to enhance the determination of theDM-RS antenna port(s) associated with PDCCH reception in theRRC_CONNECTED state.

FIG. 23 is an example of a determination of a reference signal to beused for downlink reception(s) in the RRC_CONNECTED state. A wirelessdevice may perform an SDT and/or its associated one or more subsequenttransmissions. The wireless device may receive, via PDCCH, DCI duringthe SDT and/or its associated one or more subsequent transmissions. TheDCI may comprise CRC parity bits scrambled with an RNTI (e.g., SDT-RNTI,C-RNTI, and/or the like) used for PDCCH monitoring in aNon-RRC_CONNECTED state. The DCI may comprise a downlink assignment ofPDSCH in the Non-RRC_CONNECTED. The wireless device may receive, via thePDSCH and based on the downlink assignment, a message (e.g., a downlinktransport block). The message may indicate that the wireless devicetransitions to an RRC_CONNECTED state from the Non-RRC_CONNECTED. Themessage may be an RRC message. The message may be an RRC setup message.The message may be an RRC resume message. The wireless device may make aconnection (e.g., transition to the RRC_CONNECTED state) after or inresponse to the message. In this case, the wireless device may notperform a random access procedure and/or initial access procedure. Forexample, the wireless device may make the connection (e.g., transitionto the RRC_CONNECTED state) not based on (e.g., not via and/or without)a random access procedure and/or initial access procedure. In this case,the RRC_CONNECTED without the random access procedure and/or the initialaccess procedure may result in missing a reference signal to be used fordownlink reception(s) (e.g., determination of DM-RS antenna port(s) forPDCCH reception) in the RRC_CONNECTED state.

FIG. 24 is an example of a determination of a reference signal to beused for downlink reception(s) in the RRC_CONNECTED state. A wirelessdevice may perform a random access procedure and/or an initial accessprocedure. The wireless device may determine (select, and/or identify) afirst RS among one or more first RSs, e.g., during the random accessprocedure and/or the initial access procedure. The wireless device mayperform an SDT in a Non-RRC_CONNECTED state after the random accessprocedure and/or the initial access procedure. The wireless device mayperform one or more subsequent transmission of an SDT in aNon-RRC_CONNECTED state after the random access procedure and/or theinitial access procedure. The wireless device may determine (select,and/or identify) a second RS among one or more second RSs during the SDTand/or during the one or more subsequent transmissions. The one or morefirst RSs may be the same to the one or more second RSs. The one or morefirst RSs may be different from the one or more second RSs. The wirelessdevice may receive a message indicating a transition to an RRC_CONNECTEDstate during an SDT and/or one or more subsequent transmission of anSDT. The wireless device may transition to an RRC_CONNECTED state inresponse to receiving the message. The wireless device may determine areference signal to be used for downlink reception(s) in theRRC_CONNECTED state. For example, the wireless device may use thereference signal to determine antenna configuration parameters (e.g.,DM-RS antenna port) of the one or more downlink reception(s), e.g.,PDCCH reception and/or PDSCH reception. The first RS may be outdated.The wireless environment when the wireless device selects the first RSmay be different from the one when the wireless device determines areference signal to be used for downlink reception(s) in theRRC_CONNECTED state. The wireless device may determine (and/or select),based on existing technologies, the first RS as the reference signal tobe used for downlink reception(s) in the RRC_CONNECTED state. Forexample, the wireless device may determine that DM-RS antenna port(s)associated with PDCCH and/or PDSCH receptions in the RRC_CONNECTED stateis quasi co-located with the first RS (e.g., SS/PBCH block of the firstRS and/or the CSI-RS resource of the first RS). The wireless device mayreceive, based on the first RS and/or the DM-RS antenna port(s), adownlink signal (e.g., DCI) via the PDCCH and/or a downlink transportblock via the PDSCH.

In example embodiment(s), a wireless device may use a DL RS selected viaan SDT and/or one or more subsequent transmissions of an SDT todetermine antenna configuration parameter(s) of downlink reception(s) inan RRC_CONNECTED state. For example, the wireless environment when thewireless device selects the DL RS may be substantially similar (orsubstantially the same) to the one when the wireless device may performthe downlink reception(s), e.g., with respect to at least one of Dopplershift, Doppler spread, average delay, delay spread, and/or spatial RXparameter(s). The wireless device may determine that DM-RS antennaport(s) used for the downlink reception(s) is quasi-co-located with theDL RS. Using the DL RS selected/determined via the SDT in aNon-RRC_CONNECTED state for the downlink reception(s) in anRRC_CONNECTED state may improve performance in transmission and/orreception performed in the RRC_CONNECTED state.

In example embodiment(s), a wireless device may determine, based on DLRS(s) (e.g., the SS/PBCH block or the CSI-RS resource) identified and/orselected during an SDT and/or its associated one or more subsequenttransmissions, DM-RS antenna port(s) associated with downlinkreception(s) (e.g., PDCCH reception, PDSCH reception, and/or CORESET ofPDCCH) in the RRC_CONNECTED state. In example embodiment(s), a wirelessdevice may determine, based on DL RS(s) (e.g., the SS/PBCH block or theCSI-RS resource) that the wireless device most recently identifiedand/or selected, DM-RS antenna port(s) associated with the downlinkreception(s) in the RRC_CONNECTED state. For example, DL RS(s) (e.g.,the SS/PBCH block or the CSI-RS resource) may be identified and/orselected in a most recent of an SDT and/or its associated one or moresubsequent transmissions; the initial access procedure (an MIB (or SIB)reception/acquisition); and/or the random access procedure. This resultin improving a performance in transmission and/or reception performed inthe RRC_CONNECTED state.

FIG. 25 is an example of a determination of a reference signal to beused for downlink reception(s) in the RRC_CONNECTED state. A wirelessdevice may perform an SDT and/or its associated one or more subsequenttransmissions. The wireless device may receive, via PDCCH, DCI duringthe SDT and/or its associated one or more subsequent transmissions. TheDCI may comprise CRC parity bits scrambled with an RNTI (e.g., SDT-RNTI,C-RNTI, and/or the like) used for PDCCH monitoring in aNon-RRC_CONNECTED state. The DCI may comprise a downlink assignment ofPDSCH. The wireless device may receive, via the PDSCH and based on thedownlink assignment, a message (e.g., a downlink transport block) in theNon-RRC_CONNECTED. The message may indicate that the wireless devicetransitions to an RRC_CONNECTED state from the Non-RRC_CONNECTED. Themessage may be an RRC message. The message may be an RRC setup message.The message may be an RRC resume message. The wireless device may make aconnection (e.g., transition to the RRC_CONNECTED state) after or inresponse to the message. In this case, the wireless device may notperform a random access procedure and/or initial access procedure forthe transition to the RRC_CONNECTED state. For example, the wirelessdevice may make the connection (e.g., transition to the RRC_CONNECTEDstate) not based on (e.g., not via and/or without) a random accessprocedure and/or initial access procedure. In this case, the wirelessmay perform one or more transmission(s) in the RRC_CONNECTED state basedon an RS selected during on the one or more transmission(s) (e.g., theSDT and/or its associated one or more subsequent transmission(s)) inNon-RRC_CONNECTED. For example, the wireless device may determine thatDM-RS antenna port(s) for reception of PDCCH and/or PDSCH in theRRC_CONNECTED state is quasi co-located with the RS (e.g., SS/PBCH blockof the first RS and/or the CSI-RS resource of the first RS). Forexample, the RS may be a DL RS indicated by an RRC release message thatcomprising resource configuration parameters of the SDT and/or itsassociated one or more subsequent transmissions. For example, the RS maybe a DL RS that the wireless device selects, among one or more DL RSsand based on RSRPs of the one or more DL RSs, for the SDT and/or itsassociated one or more subsequent transmissions.

FIG. 26 is an example of a determination of a reference signal to beused for downlink reception(s) in the RRC_CONNECTED state. A wirelessdevice may perform an initial access procedure (an MIB (or SIB)reception/acquisition) and/or a random access procedure. The wirelessdevice may determine (select, and/or identify) a first RS among one ormore first RSs, e.g., during the random access procedure and/or theinitial access procedure. The wireless device may perform an SDT in aNon-RRC_CONNECTED state after the random access procedure and/or theinitial access procedure. The wireless device may perform one or moresubsequent transmission of an SDT in a Non-RRC_CONNECTED state after therandom access procedure and/or the initial access procedure. Thewireless device may determine (select, and/or identify) a second RSamong one or more second RSs during the SDT and/or during the one ormore subsequent transmissions. The one or more first RSs may be the sameto the one or more second RSs. The one or more first RSs may bedifferent from the one or more second RSs. The wireless device mayreceive a message indicating a transition to an RRC_CONNECTED stateduring an SDT and/or one or more subsequent transmission of an SDT. Thewireless device may transition to an RRC_CONNECTED state in response toreceiving the message. The wireless device may determine a referencesignal to be used for downlink reception(s) in the RRC_CONNECTED state.For example, the wireless device may use the reference signal todetermine antenna configuration parameters (e.g., DM-RS antenna port) ofthe one or more transmission(s), e.g., PDCCH reception and/or PDSCHreception. The first RS may be outdated. For example, the wirelessenvironment when the wireless device selects the first RS may bedifferent from the one when the wireless device determines a referencesignal to be used for downlink reception(s) in the RRC_CONNECTED state.The wireless device may determine (and/or select) the second RS as thereference signal to be used for downlink reception(s) in theRRC_CONNECTED state. For example, the wireless device may determine thatDM-RS antenna port(s) associated with PDCCH and/or PDSCH receptions inthe RRC_CONNECTED state is quasi co-located with the second RS (e.g.,SS/PBCH block of the second RS and/or the CSI-RS resource of the secondRS). The wireless device may receive, based on the second RS and/or theDM-RS antenna port(s), a downlink signal (e.g., DCI) via the PDCCHand/or a downlink transport block via the PDSCH. For example, the secondRS may be a DL RS indicated by an RRC release message that comprisingresource configuration parameters of the SDT and/or its associated oneor more subsequent transmissions. For example, the second RS may be a DLRS that the wireless device selects, among one or more DL RSs and basedon RSRPs of the one or more DL RSs, for the SDT and/or its associatedone or more subsequent transmissions.

In an example, a wireless device may determine monitoring occasions forPDCCH candidate(s) in an RRC_CONNECTED state. For example, the PDCCHcandidate(s) may comprise a PDCCH candidate of at least one ofType0-PDCCH CSS, Type0A-PDCCH CSS, Type1-PDCCH CSS, Type2-PDCCH CSS,Type3-PDCCH CSS, and/or a USS set. The at least one may be associatedwith a search space having a particular identifier (e.g., searchspaceID= predefined and/or configured value). For example, the search space beconfigured with searchspaceID = 0. For example, the search space beconfigured with searchspaceID that is other than zero. In anRRC_CONNECTED state, the wireless device may determine to monitor PDCCHcandidates via monitoring occasion(s) associated with a DL RS. Forexample, each of the monitoring occasion(s) may be associated with oneof one or more DL RSs (that comprising the DL RS). The associationbetween the monitoring occasions(s) and the DL RS may be predefined,semi-statically configured, and/or based on a combination thereof. Thewireless device may determine that DM-RS antenna port(s) used fordownlink reception that the wireless device receive via the monitoringoccasions(s) is quasi-co-located with the DL RS, e.g., if the monitoringoccasion(s) associated with a DL RS. For example, the DL RS may be aparticular SSB and/or CSI-RS (e.g., CSI-RS resource of the DL RS). TheDL RS may be the one indicated by an activation command (e.g., MAC CE)received from a base station. The activation command may indicate a TCIstate of a BWP (e.g., active BWP) that comprises a CORESET (e.g., with aparticular index value). The TCI state may comprise a CSI-RS that may bequasi-co-located with the DL RS (e.g., SS/PBCH block of the second RSand/or the CSI-RS resource of the second RS). The DL RS may be the onethat the wireless device may determine or select (or identify) during aninitial access procedure (an MIB (or SIB) reception/acquisition) and/ora random access procedure. The DL RS may be the one that the wirelessdevice may determine or select (or identify) during an SDT and/or one ormore subsequent transmissions performed in a Non-RRC_CONNECTED state.For example, the wireless device may determine the DL RS by the mostrecent one (e.g., the most recent one determined, selected, indicated,and/or identified) among a first DL RS indicated by the activationcommand, a second DL RS selected during the initial access procedure (anMIB (or SIB) reception/acquisition) and/or the random access procedure,and/or a third DL RS selected during the SDT (and/or one or moresubsequent transmissions). For example, the wireless device may monitorPDCCH candidates via monitoring occasion(s) associated with a DL RS thatis determined by the most recent of the activation command, the initialaccess procedure (an MIB (or SIB) reception/acquisition) and/or therandom access procedure, and/or the SDT (and/or one or more subsequenttransmissions). For example, if the SDT (and/or one or more subsequenttransmissions) is the most recent one among receiving the activationcommand, performing the random access procedure, and/or the SDT (and/orone or more subsequent transmissions), and the SDT (and/or one or moresubsequent transmissions), the DL RS may be the one that the wirelessdevice may determine or select (or identify) during the SDT and/or oneor more subsequent transmissions performed in a Non-RRC_CONNECTED state.

In an example, a wireless device may determine that DM-RS antennaport(s) associated with downlink receptions (e.g., PDCCH and/or PDSCH)in an RRC_CONNECTED state is quasi co-located with a DL RS (e.g., an SSBand/or CSI-RS resource of the DL RS) that the wireless device determines(e.g., selects and/or identified) during an SDT and/or one or moresubsequent transmission of an SDT. For example, a wireless device maydetermine that DM-RS antenna port(s) associated with downlink receptions(e.g., PDCCH and/or PDSCH) is quasi co-located with a DL RS (e.g., anSSB and/or CSI-RS resource of the DL RS) that the wireless devicedetermines (e.g., selects and/or identified) during an SDT and/or one ormore subsequent transmission of an SDT if an RRC state of the wirelessdevice is transitioned to the RRC_CONNECTED state via the SDT and/or oneor more subsequent transmission. A CORESET of the downlink receptionsmay have a particular identifier value predefined and/or semi-staticallyconfigured. The particular identifier value may be zero and/or any valueother than zero. For example, a wireless device may determine that DM-RSantenna port(s) associated with the downlink receptions (e.g., PDCCHand/or PDSCH) is quasi co-located with the DL RS, e.g., if the wirelessdevice does not receive a configuration of TCI state(s) (e.g., bytci-StatesPDCCH-ToAddList and tci-StatesPDCCH-ToReleaseList) for aCORESET of the downlink receptions. For example, a wireless device maydetermine that DM-RS antenna port(s) associated with the downlinkreceptions (e.g., PDCCH and/or PDSCH) is quasi co-located with the DLRS, e.g., if the wireless device receives (e.g., bytci-StatesPDCCH-ToAddList and tci-StatesPDCCH-ToReleaseList) aconfiguration (e.g., initial configuration) of one or more TCI states(e.g., more than one TCI states) for a CORESET of the downlinkreceptions and/or does not received an activation command (e.g., MAC CE)for one of the one or more TCI states.

In an example, a wireless device may determine that DM-RS antennaport(s) associated with downlink receptions (e.g., PDCCH and/or PDSCH)and/or associated with a CORESET of the downlink receptions in anRRC_CONNECTED state is quasi co-located with a DL RS (e.g., an SSBand/or CSI-RS resource of the DL RS). The DL RS may be a first DL RS(e.g., an SSB and/or CSI-RS resource of the DL RS) that the wirelessdevice determines (e.g., selects and/or identified) during a most recentSDT and/or most recent one or more subsequent transmission of an SDT.

In an example, a wireless device may determine that DM-RS antennaport(s) associated with downlink receptions (e.g., PDCCH and/or PDSCH)and/or associated with a CORESET of the downlink receptions in anRRC_CONNECTED state is quasi co-located with a DL RS (e.g., an SSBand/or CSI-RS resource of the DL RS). The DL RS may be a first DL RS(e.g., an SSB and/or CSI-RS resource of the DL RS) that the wirelessdevice determines (e.g., selects and/or identified) during an SDT (e.g.,a most recent SDT) and/or one or more subsequent transmissions (e.g.,most recent one or more subsequent transmissions) of an SDT, e.g., if anRRC state of the wireless device is transitioned to the RRC_CONNECTEDstate via the SDT and/or one or more subsequent transmission.

In an example, a wireless device may determine that DM-RS antennaport(s) associated with downlink receptions (e.g., PDCCH and/or PDSCH)and/or associated with a CORESET of the downlink receptions in anRRC_CONNECTED state is quasi co-located with a DL RS (e.g., an SSBand/or CSI-RS resource of the DL RS). The DL RS may be a first DL RS(e.g., an SSB and/or CSI-RS resource of the DL RS) that the wirelessdevice determines (e.g., selects and/or identified) during an SDT (e.g.,a most recent SDT) and/or one or more subsequent transmissions (e.g.,most recent one or more subsequent transmissions) of an SDT, e.g., if anRRC state of the wireless device is transitioned to the RRC_CONNECTEDstate via the SDT and/or one or more subsequent transmission and/or ifthe wireless device does not receive an activation command (e.g., MACCE) indicating a TCI state for the CORESET after the SDT (e.g., a mostrecent SDT) and/or the one or more subsequent transmissions (e.g., mostrecent one or more subsequent transmissions) of the SDT.

In an example, a wireless device may determine that DM-RS antennaport(s) associated with downlink receptions (e.g., PDCCH and/or PDSCH)and/or associated with a CORESET of the downlink receptions in anRRC_CONNECTED state is quasi co-located with a DL RS (e.g., an SSBand/or CSI-RS resource of the DL RS). The DL RS may be a first DL RS(e.g., an SSB and/or CSI-RS resource of the DL RS) that the wirelessdevice determines (e.g., selects and/or identified) during an SDT (e.g.,a most recent SDT) and/or one or more subsequent transmissions (e.g.,most recent one or more subsequent transmissions) of an SDT. The DL RSmay be a second DL RS (e.g., an SSB and/or CSI-RS resource of the DL RS)that the wireless device determines (e.g., selects and/or identified)during a random access procedure (e.g., a most recent random accessprocedure) and/or an (e.g., most recent) initial access procedure (e.g.,MIB and/or SIB acquisition). The wireless device may determine the DL RSat least between the first DL RS and the second DL RS based on which DLRS (e.g., first DL RS and the second DL RS) the wireless devicedetermines (e.g., selects and/or identified) later (e.g., the mostrecent). For example, the wireless device may determine the first DL RSas the DL RS, e.g., if the wireless device performs the SDT (e.g., amost recent SDT) and/or the one or more subsequent transmissions (e.g.,most recent one or more subsequent transmissions) of the SDT after therandom access procedure (e.g., a most recent random access procedure)and/or the (e.g., most recent) initial access procedure (e.g., MIBand/or SIB acquisition). For example, the wireless device may determinethe second DL RS as the DL RS, e.g., if the wireless device performs theSDT (e.g., a most recent SDT) and/or the one or more subsequenttransmissions (e.g., most recent one or more subsequent transmissions)of the SDT before the random access procedure (e.g., a most recentrandom access procedure) and/or the (e.g., most recent) initial accessprocedure (e.g., MIB and/or SIB acquisition).

For example, the wireless device may determine the first DL RS as the DLRS, e.g., if the wireless device performs the SDT (e.g., a most recentSDT) and/or the one or more subsequent transmissions (e.g., most recentone or more subsequent transmissions) of the SDT after the random accessprocedure (e.g., a most recent random access procedure) and/or the(e.g., most recent) initial access procedure (e.g., MIB and/or SIBacquisition), if an RRC state of the wireless device is transitioned tothe RRC_CONNECTED state via the SDT and/or one or more subsequenttransmission, and/or if the wireless device does not receive anactivation command (e.g., MAC CE) indicating a TCI state for the CORESETafter the SDT (e.g., a most recent SDT) and/or the one or moresubsequent transmissions (e.g., most recent one or more subsequenttransmissions) of the SDT.

In an example, a wireless device may determine that DM-RS antennaport(s) of downlink receptions (e.g., PDCCH, CORESET of PDCCH and/orPDSCH) in an RRC_CONNECTED state are quasi co-located with a DL RS(e.g., an SSB and/or CSI-RS resource of the DL RS). The DL RS is the onethat the wireless device determines (e.g., selects and/or identified)during an SDT and/or one or more subsequent transmission of an SDT. TheDM-RS antenna port(s) may be quasi co-located with the DL RS withrespect to at least one of Doppler shift, Doppler spread, average delay,delay spread, and/or spatial RX parameter(s). For example, The DM-RSantenna port(s) may be quasi co-located with the DL RS with respect toQCL-Type A (e.g., Doppler shift, Doppler spread, average delay, and/ordelay spread) and/or QCL-TypeD (e.g., spatial RX parameter(s)). Forexample, a wireless device may determine that DM-RS antenna port(s)associated with downlink receptions (e.g., PDCCH and/or PDSCH) is quasico-located with a DL RS (e.g., an SSB and/or CSI-RS resource of the DLRS) that the wireless device determines (e.g., selects and/oridentified) during an SDT and/or one or more subsequent transmission ofan SDT if an RRC state of the wireless device is transitioned to theRRC_CONNECTED state via the SDT and/or one or more subsequenttransmission. For example, a wireless device may determine that DM-RSantenna port(s) associated with the downlink receptions (e.g., PDCCHand/or PDSCH) is quasi co-located with the DL RS, e.g., if the wirelessdevice does not receive a configuration of TCI state(s) for the downlinkreceptions. For example, a wireless device may determine that DM-RSantenna port(s) associated with the downlink receptions (e.g., PDCCH,CORESET of PDCCH, and/or PDSCH) is quasi co-located with the DL RS,e.g., if the wireless device receives a configuration (e.g., initialconfiguration) of one or more TCI states (e.g., more than one TCIstates) for the downlink receptions and/or does not received anactivation command (e.g., MAC CE) for one (e.g., a TCI state for thedownlink receptions) of the one or more TCI states.

According to an example embodiment, a wireless device may receive afirst message. The first message may indicate a transition to a radioresource control (RRC) inactive state. The first message may indicateone or more uplink grants for transmission during the RRC inactivestate. The wireless device may transmit, based on one of the one or moreuplink grants and a first downlink reference signal (RS), a firsttransport block. The wireless device may receive, based on thetransmitting the first transport block, a second message. The secondmessage may indicate a transition to an RRC connected state. Thewireless device may determine, based on the first downlink RS, one ormore antenna configuration parameters for a downlink control channel.The wireless device may receive, via the downlink control channel andusing the one or more antenna configuration parameters, downlink controlinformation. The wireless device may transmit, via a radio resourceindicated by the downlink control information, an uplink signal.

For example, the first message may indicate the first downlink RS fortransmission via the one or more uplink grants. For example, thewireless device may determine the first downlink RS among one or moredownlink RSs indicated by the first message. For example, thedetermining the first downlink RS may be based on RSRP values of the oneor more downlink RSs. For example, the determining the first downlink RSmay be based on a RSRP value of the first downlink RS, the RSRP valuebeing larger than an RSRP threshold value. For example, the determiningthe first downlink RS may be based on a RSRP value of the first downlinkRS, the RSRP value being the largest among the RSRP values. For example,the receiving the second message may be during the RRC inactive state.For example, the wireless device may start a time window in response totransmitting the first transport block. The wireless device may receive,during the time window, downlink control information comprising downlinkassignment of the second message. For example, the wireless device maymonitor, based on the one or more antenna configuration parameters, thedownlink control channel of a control resource set (CORESET) in the RRCconnected state. For example, the CORESET may be configured forreceiving one or more system information blocks. For example, theCORESET may be configured for one or more common search space sets. Forexample, the one or more antenna configuration parameters may comprise ademodulation reference signal (DM-RS) antenna port associated with areception of the downlink control channel of the CORESET. For example,the determining the one or more antenna configuration parameters maycomprise a demodulation reference signal (DM-RS) antenna port associatedwith a reception of the downlink control channel of the CORESET. Forexample, the DM-RS antenna port may be quasi co-located with an SS/PBCHblock of the first downlink RS. For example, the DM-RS antenna port maybe quasi co-located with a CSI-RS resource of the first downlink RS. Forexample, the determining the one or more antenna configurationparameters may be in response not receiving a transmission communicationinformation state for a CORESET of the downlink control channel. Forexample, the determining the one or more antenna configurationparameters may be in response not receiving an activation indication ofa transmission communication information state for a CORESET of thedownlink control channel. For example, the uplink signal may comprise asecond transport block. For example, the uplink signal may compriseuplink control information. For example, the uplink signal may comprisea sounding RS.

According to an example embodiment, a wireless device may receive afirst message. The first message may indicate a transition to a radioresource control (RRC) connected state from the RRC inactive state. Thewireless device may determine one or more antenna configurationparameters for a downlink control channel of a control resource set(CORESET) in the RRC connected state, wherein the one or more antennaconfiguration parameters is based on a downlink reference signal (RS)used later between a first downlink RS selected during a random accessprocedure; and a second downlink RS used for transmission via one ormore configured grants in the RRC inactive state. The wireless devicemay receive, via the downlink control channel and using the one or moreantenna configuration parameters, downlink control information.

According to an example embodiment, a wireless device may receive afirst message indicating a transition to a radio resource control (RRC)connected state from the RRC inactive state. The wireless device maydetermine one or more antenna configuration parameters for a downlinkcontrol channel of a control resource set (CORESET) in the RRC connectedstate. For example, the one or more antenna configuration parameters maybe based on a downlink reference signal (RS). For example, the downlinkRS may be, in response to receiving the first message via a randomaccess procedure, a first downlink RS selected during the random accessprocedure. For example, the downlink RS may be, in response to receivingthe first message based on one or more configured grants in the RRCinactive state, a second downlink RS selected for transmission via theone or more configured grants. The wireless device may receive, via thedownlink control channel and using the one or more antenna configurationparameters, downlink control information.

According to an example embodiment, a base station may transmit a firstmessage. The first message may indicate a transition to a radio resourcecontrol (RRC) inactive state. The first message may indicate one or moreuplink grants for transmission during the RRC inactive state. The basestation may receive, based on one of the one or more uplink grants and afirst downlink reference signal (RS), a first transport block. The basestation may transmit, based on the receiving the first transport block,a second message indicating a transition to an RRC connected state. Thebase station may determine, based on the first downlink RS, one or moreantenna configuration parameters for a downlink control channel. Thebase station may transmit, via the downlink control channel and usingthe one or more antenna configuration parameters, downlink controlinformation. The base station may receive, via a radio resourceindicated by the downlink control information, an uplink signal.

For example, the first message may indicate the first downlink RS fortransmission via the one or more uplink grants. For example, the basestation may determine the first downlink RS among one or more downlinkRSs indicated by the first message. For example, the determining thefirst downlink RS may be based on RSRP values of the one or moredownlink RSs. For example, the determining the first downlink RS may bebased on a RSRP value of the first downlink RS, the RSRP value beinglarger than an RSRP threshold value. For example, the determining thefirst downlink RS may be based on a RSRP value of the first downlink RS,the RSRP value being the largest among the RSRP values. For example, thetransmitting the second message may be during the RRC inactive state.For example, the base station may start a time window in response toreceiving the first transport block. For example, the base station maytransmit, during the time window, downlink control informationcomprising downlink assignment of the second message. For example, theone or more antenna configuration parameters may be for a controlresource set (CORESET) of the downlink control channel in the RRCconnected state. For example, the CORESET may be configured forreceiving one or more system information blocks. For example, theCORESET may be configured for one or more common search space sets. Forexample, the one or more antenna configuration parameters may comprise ademodulation reference signal (DM-RS) antenna port associated with areception of the downlink control channel of the CORESET. For example,the determining the one or more antenna configuration parameters maycomprise a demodulation reference signal (DM-RS) antenna port associatedwith a transmission of the downlink control channel of the CORESET. Forexample, the DM-RS antenna port may be quasi co-located with an SS/PBCHblock of the first downlink RS. For example, the DM-RS antenna port maybe quasi co-located with a CSI-RS resource of the first downlink RS. Forexample, the determining the one or more antenna configurationparameters may be in response not transmitting a transmissioncommunication information state for a CORESET of the downlink controlchannel. For example, the determining the one or more antennaconfiguration parameters may be in response not transmitting anactivation indication of a transmission communication information statefor a CORESET of the downlink control channel. For example, the uplinksignal may comprise a second transport block. For example, the uplinksignal may comprise uplink control information. For example, the uplinksignal may comprise a sounding RS.

What is claimed is:
 1. A wireless device comprising: one or moreprocessors; and memory storing instructions that, when executed by theone or more processors, cause the wireless device to: receive a radioresource control (RRC) release message indicating: one or moreconfigured grants for small data transmission (SDT) in an RRC inactivestate; and one or more synchronization signal and physical broadcastchannel blocks (SSBs) used for the SDT; receive downlink controlinformation based on a demodulation reference signal (DM-RS) antennaport for downlink control channel reception being quasi co-located withan SSB, of the one or more SSBs, selected during a most recent SDT,wherein the downlink control information indicates uplink radioresources; and transmit a transport block via the uplink radioresources.
 2. The wireless device of claim 1, wherein the instructionsfurther cause the wireless device to select, during the most recent SDT,the SSB based on a reference signal received power of the SSB beinglarger than a power threshold value, wherein the RRC release messagecomprises the power threshold value.
 3. The wireless device of claim 1,wherein the instructions further cause the wireless device to transmit,during the most recent SDT and in the RRC inactive state, uplink datavia an uplink radio resource indicated by a configured grant, of the oneor more configured grants, associated with the SSB.
 4. The wirelessdevice of claim 3, wherein the RRC release message indicates theconfigured grant being associated with the SSB.
 5. The wireless deviceof claim 1, wherein the instructions further cause the wireless deviceto determine the DM-RS antenna port for the downlink control channelreception being quasi co-located with the SSB selected during the mostrecent SDT.
 6. The wireless device of claim 4, wherein the DM-RS antennaport is determined based on a parameter, indicating a transmissionconfiguration indication (TCI) state for the downlink control channelreception, not being received before the DM-RS antenna port isdetermined.
 7. The wireless device of claim 4, wherein determining theDM-RS antenna port being quasi co-located with the SSB is in response tothe SSB being a most recent of the SSB and one or more second SSBidentified during a random access procedure.
 8. The wireless device ofclaim 7, wherein the random access procedure indicates: a most recentrandom access procedure; or an initial access procedure comprising therandom access procedure.
 9. The wireless device of claim 1, wherein thedownlink control channel reception comprises a physical downlink controlchannel reception in a control resource set (CORESET).
 10. The wirelessdevice of claim 1, wherein the downlink control channel reception is forthe wireless device in the RRC inactive state or in an RRC connectedstate.
 11. A non-transitory computer-readable medium comprisinginstructions that, when executed by one or more processors of a wirelessdevice, cause the wireless device to: receive a radio resource control(RRC) release message indicating: one or more configured grants forsmall data transmission (SDT) in an RRC inactive state; and one or moresynchronization signal and physical broadcast channel blocks (SSBs) usedfor the SDT; receive downlink control information based on ademodulation reference signal (DM-RS) antenna port for downlink controlchannel reception being quasi co-located with an SSB, of the one or moreSSBs, selected during a most recent SDT, wherein the downlink controlinformation indicates uplink radio resources; and transmit a transportblock via the uplink radio resources.
 12. The non-transitorycomputer-readable medium of claim 11, wherein the instructions furthercause the wireless device to select, during the most recent SDT, the SSBbased on a reference signal received power of the SSB being larger thana power threshold value, wherein the RRC release message comprises thepower threshold value.
 13. The non-transitory computer-readable mediumof claim 11, wherein the instructions further cause the wireless deviceto select, during the most recent SDT, the SSB based on a referencesignal received power of the SSB being larger than a power thresholdvalue, wherein the RRC release message comprises the power thresholdvalue.
 14. The non-transitory computer-readable medium of claim 11,wherein the instructions further cause the wireless device to transmit,during the most recent SDT and in the RRC inactive state, uplink datavia an uplink radio resource indicated by a configured grant, of the oneor more configured grants, associated with the SSB.
 15. Thenon-transitory computer-readable medium of claim 11, wherein theinstructions further cause the wireless device to determine the DM-RSantenna port for the downlink control channel reception being quasico-located with the SSB selected during the most recent SDT.
 16. Thenon-transitory computer-readable medium of claim 15, wherein the DM-RSantenna port is determined based on a parameter, indicating atransmission configuration indication (TCI) state for the downlinkcontrol channel reception, not being received before the DM-RS antennaport is determined.
 17. The non-transitory computer-readable medium ofclaim 15, wherein determining the DM-RS antenna port being quasico-located with the SSB is in response to the SSB being a most recent ofthe SSB and one or more second SSB identified during a random accessprocedure.
 18. A base station comprising: one or more processors; andmemory storing instructions that, when executed by the one or moreprocessors, cause the base station to: transmit a radio resource control(RRC) release message indicating: one or more configured grants forsmall data transmission (SDT) in an RRC inactive state; and one or moresynchronization signal and physical broadcast channel blocks (SSBs) usedfor the SDT; transmit downlink control information based on ademodulation reference signal (DM-RS) antenna port for downlink controlchannel reception being quasi co-located with an SSB, of the one or moreSSBs, selected during a most recent SDT, wherein the downlink controlinformation indicates uplink radio resources; and receive a transportblock via the uplink radio resources.
 19. The base station of claim 18,wherein the instructions further cause the base station to receive,during the most recent SDT and in the RRC inactive state, uplink datavia an uplink radio resource indicated by a configured grant, of the oneor more configured grants, associated with the SSB.
 20. The base stationof claim 18, wherein the downlink control channel reception comprises aphysical downlink control channel reception in a control resource set(CORESET).